Hi, On Wed, May 21, 2014 at 1:38 AM, frantisek holop <[email protected]> wrote: > hmm, on Tue, May 20, 2014 at 10:39:58PM +0200, Remi Pointel said that >> could you base your diff with mine I sent recently (to update to 1.6.4) to >> have this port working with python 3 too). > > my personal opinion is that we should keep > 1.6.* as it is. py3-django and the few > django related projects that have any py3 > support are not suitable for production > and the dust is far from settling. > i think that a port should not (unless marked > snapshot, etc) install unstable experimental > code for a framework. anyone who wants > to tinker can pip them. > > if i have read the 1.6 release notes correctly, > python3.4 will not be supported until 1.7 and > i would target that one for py3-django by > which time i expect many django related projects > to have stable py3- versions as well. 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. > > > i was also wondering, was the basehttp.py > local patch ever pushed upstream? was it > rejected? Yes, I tried pushing it upstream some time ago but they didn't like how it was constructed nor did they do anything with it. I created that patch to get rid of an erroneous error message that occurred when hitting Ctrl-C to exit the test server (which is how they instruct you to shut it off). I wouldn't say it is crucial but it makes things less scary when testing. BTW, the patch you submitted didn't update that patch correctly. > > and lastly, what will be the solution for not > duplicating documentation between py- and py3- > packages? > > -f > -- > lsd will make your cga screen display 16.2 million colors > I tried your patch on a fresh machine and besides the local patch not updating, the unit test is still failing for me for the test_template_loader_postmortem_notreadable test. We were having the same issue with the 1.6.4 patch as well.
Thanks, Ryan
