Re: "Design Decision Needed" is gone. Good riddance.

On Tue, Apr 9, 2013 at 12:02 AM, Jeremy Dunck wrote: > "easy" is for people new to contributing django or to open source in > general. Your view of "easy" may be different than our intended > meaning. :) Well, fair enough. :-) Maybe I can say it like this: I found that those

Re: Django 1.5 with Python 3.2

Hi Angus, Thanks for updating me on this. Regards Radhakrishna On Tue, Apr 9, 2013 at 1:33 AM, Angus Turner wrote: > Hi, > next time you're better off asking the question in django-users, as this > mailing list is for the development of Django itself! > > Thanks >

Re: Ticket 20147 - deprecate and replace request.META

+1 for leaving META alone. On Apr 8, 2013, at 7:45 PM, Russell Keith-Magee wrote: > > On Tue, Apr 9, 2013 at 5:13 AM, Carl Meyer wrote: >> Hi Luke, >> >> On 04/08/2013 02:02 PM, Luke Plant wrote: >> > This is already the subject of a ticket, but I

Re: Ticket 20147 - deprecate and replace request.META

On 08/04/13 22:13, Carl Meyer wrote: > Although the concept of a unified "request environ" that includes HTTP > headers mashed together with various other environment and web server > info may date back to CGI, it is not outdated; in fact it is a part of > the WSGI specification too: >

Re: "Design Decision Needed" is gone. Good riddance.

On Tue, Apr 9, 2013 at 6:11 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > On 8 avr. 2013, at 23:58, Lennart Regebro wrote: > > > On Mon, Apr 8, 2013 at 4:57 PM, Jacob Kaplan-Moss > wrote: > >> Thanks, please let me know if you have

Re: Ticket 20147 - deprecate and replace request.META

On Tue, Apr 9, 2013 at 5:13 AM, Carl Meyer wrote: > Hi Luke, > > On 04/08/2013 02:02 PM, Luke Plant wrote: > > This is already the subject of a ticket, but I didn't get a response > > yet. Basically, the idea is replace things like: > > > > request.META['HTTP_ACCEPT'] > > > >

Re: "Design Decision Needed" is gone. Good riddance.

"easy" is for people new to contributing django or to open source in general. Your view of "easy" may be different than our intended meaning. :) On Mon, Apr 8, 2013 at 2:58 PM, Lennart Regebro wrote: > On Mon, Apr 8, 2013 at 4:57 PM, Jacob Kaplan-Moss

Re: "Design Decision Needed" is gone. Good riddance.

On Mon, Apr 8, 2013 at 4:57 PM, Jacob Kaplan-Moss wrote: > Thanks, please let me know if you have questions! Nope, but a suggestion: Mark new tickets as "easy pickings" by default. During the sprint I didn't find any ticket that wasn't either more than a year old (often

Re: Ticket 20147 - deprecate and replace request.META

On 08/04/13 21:17, Michael Manfre wrote: > +1 to a saner repr(request) and not having to type "HTTP_". What sort of > deprecation cycle are you thinking for this? I'm thinking the normal cycle: 1.6 - request.HEADERS added, probably a few friends too. - request._META added - accessing

Re: Ticket 20147 - deprecate and replace request.META

Hi Luke, On 04/08/2013 02:02 PM, Luke Plant wrote: > This is already the subject of a ticket, but I didn't get a response > yet. Basically, the idea is replace things like: > > request.META['HTTP_ACCEPT'] > > with > > request.HEADERS['Accept'] > > request.META should be deprecated and

Re: Ticket 20147 - deprecate and replace request.META

+1 to a saner repr(request) and not having to type "HTTP_". What sort of deprecation cycle are you thinking for this? Regards, Michael Manfre On Mon, Apr 8, 2013 at 4:02 PM, Luke Plant wrote: > Hi all, > > This is already the subject of a ticket, but I didn't get a

Re: Django 1.5 with Python 3.2

Hi, next time you're better off asking the question in django-users, as this mailing list is for the development of Django itself! Thanks Angus Turner angusisf...@gmail.com On Tue, Apr 9, 2013 at 1:49 AM, L Radhakrishna Rao wrote: > Thanks Horst. > > Even I had

Ticket 20147 - deprecate and replace request.META

Hi all, This is already the subject of a ticket, but I didn't get a response yet. Basically, the idea is replace things like: request.META['HTTP_ACCEPT'] with request.HEADERS['Accept'] request.META should be deprecated and replaced with request._META, because it is just an implementation

Re: Kickstarter for Django Admin?

It looks good, Thanks for sharing. On Wed, Apr 3, 2013 at 8:41 PM, Jason Kraus wrote: > > A RESTful api with a separate template client is exactly what hyperadmin > aims to do: https://github.com/zbyte64/django-hyperadmin > I've played around with bolting on an emberjs client

Re: Django 1.5 with Python 3.2

Thanks Horst. Even I had referred that docs, and it stuck me. I just tried to simplify it. Regards -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: Django 1.5 with Python 3.2

This is documented here: https://docs.djangoproject.com/en/dev/topics/python3/#str-and-unicode-methods:-) Cheers, Horst On Mon, Apr 8, 2013 at 4:42 PM, L Radhakrishna Rao wrote: > I was following tutorials of django book, where python 2.7 version is used. > > I am

Django 1.5 with Python 3.2

I was following tutorials of django book, where python 2.7 version is used. I am using python 3.2 version and django 1.5. The django book chapter 5 'Adding Model String Represenations' needs to be changed while publishing book for python 3.x version. The 'def__unicode__(self)' does not work

"Design Decision Needed" is gone. Good riddance.

Hi folks -- "Design decision needed" is where good tickets go to die. The idea was that someone could come by later and make the decision, but as it turns out, Someone doesn't work here. In practice, DDN tickets sat open, often for years, and just frustrated everyone. So we're getting rid of

Re: Extending the DATABASES = {'xx': {'NAME': construct to carry additional information and / or virtual names

On 8 avr. 2013, at 10:21, VernonCole wrote: > 1) re-implement the argument signature of adodbapi so that it agrees with the > recommendation for positional and keyword arguments in PEP 249, except that > the first positional argument is called "connection_string" rather

Re: currency of DATABASES = {'xx' : {'OPTIONS' = {'AUTOCOMMIT' ... flag.

On 8 avr. 2013, at 10:33, VernonCole wrote: > I am confused by the documentation. I cannot seem to figure out whether the > AUTOCOMMIT switch is a new feature on the way in, or an obsolete feature on > the road to deprecation. Defining AUTOCOMMIT = True within

currency of DATABASES = {'xx' : {'OPTIONS' = {'AUTOCOMMIT' ... flag.

I am confused by the documentation. I cannot seem to figure out whether the AUTOCOMMIT switch is a new feature on the way in, or an obsolete feature on the road to deprecation. I can easily add the feature to adodbapi, but should I do so or not? -- Vernon -- You received this message because

Re: Extending the DATABASES = {'xx': {'NAME': construct to carry additional information and / or virtual names

Thanks for the feedback. I have incorporated your suggestions into my design. There is nobody around here I can use for a design review, so, begging your forgiveness, I will have to do it here. Here is how I am setting up the prototype... 1) re-implement the argument signature of adodbapi so