Re: Python 3 and you

Jannis, that's great news indeed, I'll help with testing. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/jzva36TUYGcJ. To post to this group,

Re: Python 3 and you

@Jannis Leidel, is there some plan, tasks or something for new contributors and how could I(python developer and django user) help? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit

Re: Python 3 and you

If you want to test Linux deployment, install Ubuntu under VirtualBox: https://www.virtualbox.org/ Brian Schott bfsch...@gmail.com On Nov 8, 2011, at 11:37 AM, richard.prosser wrote: > Yes I know but Vista isn't the best platform and my laptop isn't that > hot! > > Plus I have very good

Re: Python 3 and you

Yes I know but Vista isn't the best platform and my laptop isn't that hot! Plus I have very good Unix/Linux experience, which may help. Richard On Nov 7, 2:01 pm, "Jonas H." wrote: > On 11/07/2011 12:00 PM, richard.prosser wrote: > > > I may be willing to support this. I

Re: Python 3 and you

On 11/07/2011 12:00 PM, richard.prosser wrote: I may be willing to support this. I have 18 month's of Python experience (mostly 2.4) and I have been out of work for a long time due to illness, so a project like this may look good on my CV! I have never been involved in an OS project before,

Re: Python 3 and you

I may be willing to support this. I have 18 month's of Python experience (mostly 2.4) and I have been out of work for a long time due to illness, so a project like this may look good on my CV! I have never been involved in an OS project before, though I am aware of the guidelines. At present the

Re: Python 3 and you

__enter__() and __exit__() > methods to objects where that makes sense.  If the programmer is using > an older compiler, then they will never get called, but they will be > present when someone with a new compiler uses a "with" statement.  We > cannot use "with" in mo

Re: Python 3 and you

ll never get called, but they will be present when someone with a new compiler uses a "with" statement. We cannot use "with" in module code, though, until all python 2.4 users have disappeared. Same thing when moving to Python 3.x -- you cannot use any new features, but you h

Re: Python 3 and you

On Wed, Sep 14, 2011 at 8:42 PM, Jannis Leidel wrote: > > > Anybody knows somebody who started a django/py3 port already? We should > unify our efforts. > > As I said earlier in this thread, there is now a Python 3 branch in the > Django SVN. > Thank you! Really good to see

Re: Python 3 and you

On 14.09.2011, at 19:19, Cal Leeming [Simplicity Media Ltd] wrote: > Can I ask, have the django core team already accepted that Django will > eventually be a 3.x framework, or will it be un-officially forked? Yes, the core team has identified the port to Python 3 as a needed step which is why

Re: Python 3 and you

On 14.09.2011, at 18:57, Ákos Péter Horváth wrote: > Really, I started to port that with a recursive 2to3. It is not too far from > good working. There are no big magic things, altough I think a py2 and py3 > support isn't possible from a common source tree. Some deep core improvement > is

Re: Python 3 and you

Can I ask, have the django core team already accepted that Django will eventually be a 3.x framework, or will it be un-officially forked? Personally - I'd love to see people ride the 2.x train until its last dying breath, but that's just me ;) Cal 2011/9/14 Ákos Péter Horváth

Re: Python 3 and you

Hi, On Wed, Sep 14, 2011 at 10:03 AM, Jannis Leidel wrote: > Hi all, > > After last week's sprint I wanted to get you up-to-speed about the > current state of porting Django to Python 3. > I'm very happy with this news. > As some may be aware Martin von Löwis has been working

Re: Python 3 and you

Daniel, > I wasn't trying to suggest we leave anyone behind, far from it. I > was suggesting move the code to Python 3 now, while there's less code > there (than some future date) but using 3to2[1] to help others on > Python 2.X. Since Django still supports 2.5, it's possible that this > isn't

Re: Python 3 and you

Help to cite appropriately. [1] was http://pypi.python.org/pypi/3to2. On Sep 14, 10:55 am, Daniel Lindsley wrote: > Jannis, > >    I wasn't trying to suggest we leave anyone behind, far from it. I > was suggesting move the code to Python 3 now, while there's less code >

Re: Python 3 and you

Jannis, I wasn't trying to suggest we leave anyone behind, far from it. I was suggesting move the code to Python 3 now, while there's less code there (than some future date) but using 3to2[1] to help others on Python 2.X. Since Django still supports 2.5, it's possible that this isn't even an

Re: Python 3 and you

Daniel, > "You have my sword." I want to see this happen & would love to be a > part of it. Huzzah! > A couple questions: > > * How should patches be provided? Trac? BitBucket? For now via Trac, that's why we've moved the changes into a SVN branch. Unless anyone has a better idea I could

Re: Python 3 and you

Jannis, "You have my sword." I want to see this happen & would love to be a part of it. A couple questions: * How should patches be provided? Trac? BitBucket? * Where should feedback go? This mailing list? Somewhere else? * This is further off, but once we have a ported Django, how do get

Python 3 and you

Hi all, After last week's sprint I wanted to get you up-to-speed about the current state of porting Django to Python 3. As some may be aware Martin von Löwis has been working on a port for a while [1] but only recently I've had the chance to meet with him and talk through the porting process.