Re: Re: Porting Django to Python 3.0 as a GSoC project

much time to it. In any event, by now it's pretty clear that my proposal isn't all that popular, so I'm retracting it. Thanks for all the feedback! I'll be lurking around :) Cheers, rbp -- Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> | GPG KeyId: <0x0DB1497

Re: Re: Porting Django to Python 3.0 as a GSoC project

that Python 3.0 is not that much of a moving target either. Of course, such a porting project would require following development of 2to3. rbp -- Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> | GPG KeyId: <0x0DB14978> http://isnomore.net --~--~-~--~~~

Re: Re: Porting Django to Python 3.0 as a GSoC project

s, for the reasons I explained above. The port might not be instantly suitable for a sizeable project, but that's not the only advantage that such a port would offer. Thanks again for your feedback, James! I'd love to hear more from other developers on this matter. rbp -- Rodrigo Bern

Re: Re: Porting Django to Python 3.0 as a GSoC project

king on pyk3. As for whether it should be included in trunk or as a branch, I'd like input from my would-be mentor, as well as on what concerns external dependencies that might also need porting. > Anyway, good luck with the Summer of Code. Thanks, and thanks for the feedback! :) Cheer

Porting Django to Python 3.0 as a GSoC project

be willing to mentor (or co-mentor) me on it. Thanks! rbp -- Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> | GPG KeyId: <0x0DB14978> --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django