On Wed, Dec 31, 2008 at 8:43 AM, Justin Bronn wrote:
>
>> I'll be looking into this, this week.
>> Good news is: So far so good (But I haven't tried to mix geo aggregates with
>> new aggregates yet).
>
> OK, in the GeoDjango 1.1 mercurial [1], I've merged in Russell's
> aggregation branch and mod
> OK, in the GeoDjango 1.1 mercurial [1], I've merged in Russell's
> aggregation branch and modified the aggregate geographic methods to
> internally use the new aggregation API.
Awesome,
I am gonna switch to that branch right away.
Ariel.
--~--~-~--~~~---~--~~
Y
> I'll be looking into this, this week.
> Good news is: So far so good (But I haven't tried to mix geo aggregates with
> new aggregates yet).
OK, in the GeoDjango 1.1 mercurial [1], I've merged in Russell's
aggregation branch and modified the aggregate geographic methods to
internally use the new
I could also help with arrangements for a sprint in Chicago. I'm just
starting to become involved in django development, though, so I'm not
sure what would be the best way to help out. Just wanted to let you
guys know that there are 2 more hands over here.
On Tue, Dec 30, 2008 at 2:41 PM, alex.
On Tue, Dec 30, 2008 at 2:41 PM, alex.gay...@gmail.com
wrote:
>
> For any sprint occurring before the 11th I could help arrange
> something in Chicago
Count me in. But all I'll do is try to harass the local python gurus
in to fixing my session-wizard-thing.
-Dave
--~--~-~--~~-
For any sprint occurring before the 11th I could help arrange
something in Chicago
On Dec 30, 10:43 am, Eric Holscher wrote:
> It looks like January 15 is when the Major Feature freeze happens (and
> that is in about 2 weeks). The roadmap[1] says that there will be 1.1
> sprints starting in late
I setup a git repository http://github.com/weigj/django-multidb/tree/master for
it.
I patched fields, query and manager, so Model.objects.using('db1') is work now,
like this:
users = User.objects.using('db1').filter()
for user in users:
user.save(using='db2')
Wei guangjing
- Ori
It looks like January 15 is when the Major Feature freeze happens (and
that is in about 2 weeks). The roadmap[1] says that there will be 1.1
sprints starting in late december, which has come and is quickly
fading. Just figured I would start the discussion on when/where some
sprints will be happeni
Ed Summers wrote:
> In my
> case I'm implementing an AtomPub interface for a data repository at
> the Library of Congress instead of wanting to stream XML, but the
> mechanics are the same.
Yes. It's expected to look something like this:
if request.META['Content-type'] == 'application/atom+
On Dec 30, 8:15 am, Ivan Sagalaev wrote:
> BTW, Malcolm's series have inspired me to implement (along with some
> refactoring) a file-like interface for HttpRequest[1]. With this you can
> actually pass request as a source to, say, a SAX parser and not have to
> load it entirely in memory.
Nice!
Thanks Waylan. I posted to django-users as well (still waiting, but it
is the holidays). Those blog posts of Malcolm's were very useful--
although covered ground I was already familiar with. I actually did
consider posting on django-users instead of on here, but in the end
posted here because I th
Waylan Limberg wrote:
> For a start, you may want to take a look as Malcolm's recent
> multi-part series on the subject. Note the third one with regard to
> content-types.
>
> http://www.pointy-stick.com/blog/2008/12/09/implementing-http-services-django/
> http://www.pointy-stick.com/blog/2008/12
12 matches
Mail list logo
