Re: Upcoming Django release, and the future

On 2/26/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > On 2/26/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > AFAIK, it is finished, just waiting for Adrian's ok. Is there > > something missing that I'm not aware of? > > Oh, I thought there was something missing *I* wasn't aware of :

Re: Refactoring QuerySet

Hi Malcolm, Malcolm Tredinnick schrieb: > Let's stop going down this path. This isn't a thread about whether to > switch to SQLAlchemy. If you want to work on that, there is a branch > already created and a maintainer appointed for that branch. I've got > nothing against it, but it's not an area

Re: Upcoming Django release, and the future

On 2/26/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > On 2/25/07, Rubic <[EMAIL PROTECTED]> wrote: > > In keeping with the overall theme of testing at this > > year's PyCon, it would be nice to have integrated > > testing (fixtures, ticket #2333) brought to resolution. > > I really, really,

Re: Upcoming Django release, and the future

On 2/26/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > AFAIK, it is finished, just waiting for Adrian's ok. Is there > something missing that I'm not aware of? Oh, I thought there was something missing *I* wasn't aware of :) Please go ahead and check it in! I'll focus on writing docs (and

Re: Upcoming Django release, and the future

On 2/25/07, Rubic <[EMAIL PROTECTED]> wrote: > In keeping with the overall theme of testing at this > year's PyCon, it would be nice to have integrated > testing (fixtures, ticket #2333) brought to resolution. I really, really, *really* agree, and I'm going to look at seeing if I can channel Russ

Re: Refactoring QuerySet

On 2/25/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Let's stop going down this path. This isn't a thread about whether to > switch to SQLAlchemy. If you want to work on that, there is a branch > already created and a maintainer appointed for that branch. I've got > nothing against it, but

Re: Upcoming Django release, and the future

On 2/25/07, Brian Harring <[EMAIL PROTECTED]> wrote: > http://code.djangoproject.com/ticket/3440 , Models.__init__ > refactoring. #3440 is fixed and has to do with DateQuerySet; did you mean #3438? Jacob --~--~-~--~~~---~--~~ You received this message because you

Re: Upcoming Django release, and the future

On 2/25/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > One thing comes to my mind, supporting non-ASCII characters in newforms: Since newforms will still be "new" in 0.96, I'm could take or leave these before it. I'll try to get to 'em, though. > http://code.djangoproject.com/wiki/FeatureGrou

Re: Upcoming Django release, and the future

In keeping with the overall theme of testing at this year's PyCon, it would be nice to have integrated testing (fixtures, ticket #2333) brought to resolution. It was great to briefly meet everyone over the past few days in Dallas. -- Jeff Bauer Rubicon, Inc. --~--~-~--~~---

Re: Upcoming Django release, and the future

On Sun, Feb 25, 2007 at 10:56:36PM -0600, James Bennett wrote: > If there's a bug that's been annoying the heck out of you and you want > it fixed before the release, this would be the time to speak up about > it. http://code.djangoproject.com/ticket/3440 , Models.__init__ refactoring. Fair amou

Re: Refactoring QuerySet

On Mon, 2007-02-26 at 06:08 +0100, Michael Radziej wrote: > Hi, > > Malcolm Tredinnick wrote: > > In passing, moving the query construction out of QuerySet, particularly > > if we move the database access portions out as well, will make > > integrating with SQLAlchemy easier -- since it's "just a

Re: Upcoming Django release, and the future

Hi James, James Bennett wrote: > If there's a bug that's been annoying the heck out of you and you want > it fixed before the release, this would be the time to speak up about > it. We have a fairly high concentration of Django developers all in > one place with nothing to do but code, so hopeful

Re: Refactoring QuerySet

Hi, Malcolm Tredinnick wrote: > In passing, moving the query construction out of QuerySet, particularly > if we move the database access portions out as well, will make > integrating with SQLAlchemy easier -- since it's "just another data > storage backend". If you make it a design goal, yes. Bu

Upcoming Django release, and the future

Upcoming Django release, and the future As we sit here in warm, sunny Dallas, meditating on how next year's PyCon will be in cold, cloudy Chicago, we're also getting ready to push out a new release of Django, and with that there are some things you all need to know, and as your friendly neighborh

Flash Game maker & Animation Tools for Kids and Professionals

Flash Animation - The Game making and easy learning [image: Flash animation maker - game makers] http://100stuff.com/info/flash-game-maker/ Best Flash animation softwares Flash Game Makers Game Making Tools Easy Game Making Click here.

Best Professional Designing Softwares

Professional Designing Tools & Softwares [image: 3D Designing Tools Kingdom] http://www.100stuff.com/downloads/3d_design/ *Best 3D designing Tools* *Professional Designing software* *Electronic Designings* *Electrical Circuits designing* *Civil Eng

Re: Refactoring QuerySet

On Mon, 2007-02-26 at 11:26 +1100, Malcolm Tredinnick wrote: [...] > > That said, it will be interesting to see what happens in the SQLAlchemy > branch. However, for right now, I would rather just fix our immediate > problems: moving query construction into a separate position and redoing > the m

Re: Refactoring QuerySet

On 2/25/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > I noticed today that a new GIS branch has been created, which includes a > goal to develop a custom QuerySet-derivative. There has also been a > discussion on trying to work out an API for aggregates, which seems to > be moving along, alt

Re: Refactoring QuerySet

On Sun, 2007-02-25 at 19:06 +0100, Michael Radziej wrote: > Hi Malcolm, > > I like this since a lot. Your approach to put the SQL construction into > a different query reminds me much of SQLAlchemy. A quote from their > tutorial [1]: > > """A central concept of SQLAlchemy is that it actually con

Re: Refactoring QuerySet

On Sun, 2007-02-25 at 18:21 +0100, Honza Král wrote: > On 2/25/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > > I noticed today that a new GIS branch has been created, which includes a > > goal to develop a custom QuerySet-derivative. There has also been a > > discussion on trying to work

Re: improving Atom support

James Tauber wrote: > I'm taking on the task of improving Atom support in Django, both from > the point of view of extending support for the feed format and also > implementing the Atom Publishing Protocol (APP). Hello James! This is a rather nice coincidence :-). In the coming weeks I'm abo

Free Greeting cards!

Free Greeting cards! - http://surl.in/HLFCI238206SVRAKSX-google --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To u

Free Greeting cards!

Free Greeting cards! - http://surl.in/HLFCI238206SVRAKSX-google --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To u

improving Atom support

I'm taking on the task of improving Atom support in Django, both from the point of view of extending support for the feed format and also implementing the Atom Publishing Protocol (APP). I've previously written a standalone implementation of APP so that will be the starting point. I've cre

Re: Refactoring QuerySet

Hi Malcolm, I like this since a lot. Your approach to put the SQL construction into a different query reminds me much of SQLAlchemy. A quote from their tutorial [1]: """A central concept of SQLAlchemy is that it actually contains two distinct areas of functionality, one of which builds upon the

Re: Database template loader

On 2/25/07, Jannis Leidel <[EMAIL PROTECTED]> wrote: > I now moved everything to the django.contrib.dbtemplates app and > added a utility which syncs all filesystem based templates in > TEMPLATES_DIRS to the database. The docs are now in dbtemplates.txt. Awesome :) > Could someone please explain

Re: Refactoring QuerySet

On 2/25/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > I noticed today that a new GIS branch has been created, which includes a > goal to develop a custom QuerySet-derivative. There has also been a > discussion on trying to work out an API for aggregates, which seems to > be moving along, al

Re: Database template loader

Hi all! Am 24.02.2007 um 23:30 schrieb Jacob Kaplan-Moss: > Yeah, I'd just go ahead and move it all into contrib; seems the best > place for this stuff. I now moved everything to the django.contrib.dbtemplates app and added a utility which syncs all filesystem based templates in TEMPLATES_D

Re: Upcoming changes to the Django admin

Hi, sounds very good to me. Among other things, these changes should make it much easier to implement two use cases that were always said to be outside of the scope of admin, despite being -- at least in my opinion -- very useful and common. 1. give some staff members permission to view instanc

Refactoring QuerySet

I noticed today that a new GIS branch has been created, which includes a goal to develop a custom QuerySet-derivative. There has also been a discussion on trying to work out an API for aggregates, which seems to be moving along, although I suspect the design has a bit more work required yet. Micha

Re: Regarding UTF-8 and database queries.

that should work. we´re working with this though: http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> http://www.w3.org/1999/xhtml"; xml:lang="de" lang="de"> patrick Am 25.02.2007 um 12:49 schrieb Emil Ahlbäck: > > Great, I forgot the point. > > www.w3.org/TR/xhtml1/DTD/xhtml1-

Re: Regarding UTF-8 and database queries.

Hey. Yeah I just noticed that I was in the wrong forum also. Sorry about that. If it's possible, perhaps an administrator could move it? On Feb 25, 1:14 pm, "patrick k." <[EMAIL PROTECTED]> wrote: > we?re also using UTF-8 (with umlauts and special characters) and we > don?t have any problems. > d

Re: Regarding UTF-8 and database queries.

Great, I forgot the point. http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en"> This is the start of our base.html, so that should be enough, no? On Feb 25, 1:48 pm, "Emil Ahlb�ck" <[EMAIL PROTECTED]> wrote: > Hey. Yeah I just noticed that I was in the wrong forum also. Sorry > about

Re: Regarding UTF-8 and database queries.

we�re also using UTF-8 (with umlauts and special characters) and we don�t have any problems. do you use the right content-type? btw, that question should go to "django-users". patrick Am 25.02.2007 um 11:59 schrieb Emil Ahlb�ck: > > Hello everyone. > > Recently me and a friend revived an ol

Regarding UTF-8 and database queries.

Hello everyone. Recently me and a friend revived an old project, in hope that Django will offer us a non-clusterf***y way to work, and it did. It's great, I love it. :) I have run into a problem though, after using google a bit for finding information in the documentation I decided to turn here.

Re: Upcoming changes to the Django admin

On Sun, 2007-02-25 at 00:51 -0600, Jacob Kaplan-Moss wrote: > Howdy folks -- > > After a wonderful Django meetup here at PyCon (Django: the framework > that buys you pizza), a bunch of us spun off into a little ad-hoc > sprint to talk about improvements to the Django admin. > > This email summar