Re: authentication by email

Can I ask for one change this late in the project to the 1.4 release if it's only the documentation for this bug? I'm hoping someone at PyCon might be able to "sneak this in." Can we add a note to the EmailField documentation that states that "The default 75 character max_length is not capable of

Re: authentication by email

012, at 1:52 AM, Joe & Anne Tennies wrote: > > > While, I generally agree with the current approach, especially this > close to release. I'm going to play devil's advocate for a bit. > > > > Schema migrations have been talked about for quite a while. There are at &

Re: authentication by email

;Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/djang

Re: Django participation in Google Summer of Code 2012

group. > > > To post to this group, send email to > django-developers@googlegroups.com. > > > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > > > For more options, visit this group athttp:// > groups.google.com/group/

Re: Revisiting multiline tags

Sorry all, I think I got my conversations mixed up. I was thinking this was the whitespace conversation also going on. 2012/2/26 Łukasz Rekucki <lreku...@gmail.com> > On 26 February 2012 05:55, Joe & Anne Tennies <tenn...@gmail.com> wrote: > > While this would be a

Re: Revisiting multiline tags

s group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- Joe & An

Re: start using less (and bootstrap!)

and schema revision tracking, etc.) Then include a simple implementation that can migrate databases via some script but not autodetect changes. Basically, I see a big need for Django to start providing specifications to how things -- Joe & Anne Tennies tenn...@gmail.com -- You received this m

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

So, with the current plan to add 3.x support to 1.5 and the plan to remove 2.5.x support in 1.5. Should all the exception handling blocks be converted to "except MyExceptionClass as e:" style notation then? This also removes the need for u() and b(), right? This is because 2.6.x supports u' ' and

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

om/d/msg/django-developers/-/Y8-2tS9lth4J. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com

Re: Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

is group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- Joe & Anne Tennies tenn...@gmail.com -- You received this message because you are subscribed to

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

psycopg2 won't run upper on something that's not a unicode in python 3, but it needs to be a bytestring later to have the "buffer interface" implemented. On Tue, Dec 6, 2011 at 9:05 PM, Joe & Anne Tennies <tenn...@gmail.com>wrote: > Updated: > > I thought I'd p

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

I thought I'd put in my timing numbers on my computer (F16 on a Phenom II x6): Python3 port on python 3.2.1 w/ sqlite: * Ran 4429 tests in 528.327s * FAILED (errors=1, skipped=96, expected failures=2, unexpected successes=1) + Python3 port on python 2.7.2 w/ sqlite: * Ran 4490 tests in 487.212s *

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- Joe & Anne Tennies tenn...@gmail.com -- You received this message b

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

ogle Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.g

Re: Sane defaults for Startapp and Startproject

ings.py by default. Most problems I have helping people is a default value that's not explicitly done in the settings.py, so people don't realize it's something they can override (or may need to). My criteria would be anything that could require modification (within reason) when adding or rem

Re: deprecation vs removal

I know that no one knows who I am, but I'm going to say that this is becoming a bike shed. It sounds like there's generally agreement that people need to be warned that something is going to be removed. It sounds like people that maintain code that is required to be stable and relies on other