[01:39] <stub> cjwatson: There is also that 'fades' thing  Facundo put together that builds the virtualenv on demand
[04:55] <replaceafill> hi wgrant, are you around?
[04:56] <wgrant> rpadovani: I am.
[04:56] <wgrant> Er
[04:56] <wgrant> replaceafill: ^^
[04:56] <replaceafill> :D
[04:56] <replaceafill> may i take a few minutes of your time with a lazr.restful + lazr.batchnavigation question? :)
[04:57] <replaceafill> i'm not sure if this is the right place to ask
[04:57] <replaceafill> but i've seen lazr discussed here i think...
[05:00] <lifeless> it was built for lp
[05:00] <lifeless> so seems fine to me
[05:01] <replaceafill> lifeless, thanks :)
[05:01] <replaceafill> i'm using it with a SchoolTool experiment
[05:02] <replaceafill> and i have a lazr.restful implementation running through paste
[05:02] <replaceafill> i just noticed one thing in the URLs generated in my queries
[05:03] <replaceafill> specifically the next_collection_link and prev_collection_link
[05:03] <replaceafill> they return URLs like: "next_collection_link": "http://localhost:7080/1.0/persons/...
[05:04] <replaceafill> when i get resource_type_link's and self_link's like:
[05:04] <replaceafill> "self_link": "http://localhost:7080/api/1.0/persons/student051"
[05:04] <replaceafill> which are correct, notice the /api/ part
[05:05] <replaceafill> that's from my paste configuration
[05:05]  * replaceafill is not sure he's clear enough explaining this... :(
[05:06] <replaceafill> anyway i tracked the url generation in both cases and noticed that lazr.restful generates the urls using absolutURL calls,which seems fine
[05:06] <replaceafill> but lazr.batchnavigator doesn't
[05:06] <lifeless> sounds like a bug somewhere ;)
[05:06] <lifeless> I don't recall the nuance of that code - its been ~4 years since I hacked on it
[05:06] <replaceafill> lifeless, i could be it's here: http://bazaar.launchpad.net/~lazr-developers/lazr.batchnavigator/trunk/view/head:/src/lazr/batchnavigator/_batchnavigator.py#L272
[05:06] <lifeless> wgrant: may have more recent memories
[05:06] <replaceafill> :)
[05:08] <replaceafill> i guess i just wanted to confirm it's a bug and i should just not trust those batch links
[05:08] <lifeless> it may be that batchnavigation thinks its returning html urls not api urls
[05:11] <replaceafill> i wonder if batchnavigation could use this same approach used in lazr.restful: http://bazaar.launchpad.net/~lazr-developers/lazr.restful/trunk/view/head:/src/lazr/restful/_resource.py#L2070
[05:53] <wgrant> Whoops, sorry, got called away.
[05:54] <wgrant> replaceafill: Hmm, so batchnavigator is meant to use the same request as lazr.restful.
[05:54] <wgrant> replaceafill: But it's possible you have to instantiate it directly with the right request, let me see.
[05:56] <wgrant> Hmm.
[05:58] <wgrant> replaceafill: Have you worked out what the difference between the URL generation calls is between lazr.restful itself and lazr.batchnavigator?
[05:58] <wgrant> I can't see why batchnav would be getting the wrong request.
[05:59] <wgrant> Unless you have a property that directly returns one?
[06:00] <wgrant> replaceafill: So the only way I can see that happening is if your code creates a BatchNavigator directly.
[06:00] <wgrant> If you simply declare an attribute as a collection and let lazr.restful batch it for you, it should Just Work.
[10:43] <cjwatson> https://code.launchpad.net/~cjwatson/turnip/virtualenv/+merge/274701 should be less flaky now
=== BradCrittenden is now known as Guest53960