Le 21-05-2014 10:38, frantisek holop a écrit :
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.
We could have a python3 flavor even if won't link it to the build for
the moment, it could be useful to run regress tests in python 2 and
python 3 for example, and I suppose certain people who begin a new
django project could run with Python 3 and no Python 2.
If I correctly read
https://docs.djangoproject.com/en/dev/topics/python3/, it should work
correctly in Python 3.
Also, our default Python 3 for the moment is 3.3, so no problem with
python 3 django 1.6.x.
and lastly, what will be the solution for not
duplicating documentation between py- and py3-
packages?
You could read my diff, I resolved this part:
http://marc.info/?l=openbsd-ports&m=139849280216034&w=2
Cheers,
Remi.
