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 was also wondering, was the basehttp.py local patch ever pushed upstream? was it rejected? 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
