Hi, On Wed, May 21, 2014 at 7:21 AM, frantisek holop <min...@obiit.org> wrote: > hmm, on Wed, May 21, 2014 at 06:55:01AM -0700, Ryan Boggs said that >> I wouldn't mind having a py3 flavor that targets <=3.3 with a caveat >> that it is not recommended for production use. The reason being is >> that I think there would be people here who want to get started on >> python3, at least for testing purposes. > > what is the point of encouraging > starting learning something on a > non production-ready version? My mistake. Py3 support was only experimental in django 1.5. Based on the project FAQ, py3 support is stable and production ready starting in django 1.6: https://docs.djangoproject.com/en/dev/faq/install/
> > the fundamental problem for me is the > fact that py3 compatibility does not mean > what I expect: 3.3 is ok but 3.4 is not, > while both of them are "3.x" I looked at this further yesterday and now I am debating which would be better, set the py3 flavor now to get a jump on it for those who want to get started today or wait until 1.7 comes out so there is no worry about targeting <=python3.4. Django 1.7 is currently in beta (beta4, I believe) so there shouldn't be much of a wait for that but who knows what the exact release schedule will be. Other thoughts? > > -f > -- > runtime error. should i walk? (y/n) > Thanks, Ryan
