Stuart,
I did some thinking on this as a heavy consumer, and light developer, of
Python applications.
There are 455 Python3 modules currently in the repository would would be
unreasonable to test all of them [1]. That being said there also appears
to be hesitation on importing updated modules by the OpenBSD team [2].
Given that a large percentage of these are probably out of date they may
not work with Python 3.7. I anticipate a large number of issues when
making 3.7 the default, unless modules catch up due to changes with Py3.7.
That being said I do still support that decision and think it would be a
good step forward for the ports tree. Thoughts on how this can happen?
I have tested Daniel's update to 3.7 and it seems fine for me during my
normal usage and the modules I use.
Thank you,
Edward Lopez-Acosta
[1]
$ pkg_info -Q py3- | grep -E "^py3-" -c
455
[2]
https://marc.info/?l=openbsd-ports&m=154250379325554&w=2
https://marc.info/?l=openbsd-ports&m=154232569512562&w=2
https://marc.info/?l=openbsd-ports&m=154241864207006&w=2
https://marc.info/?l=openbsd-ports&m=154241778006783&w=2
https://marc.info/?l=openbsd-ports&m=154232597012625&w=2
https://marc.info/?l=openbsd-ports&m=154247815319002&w=2
https://marc.info/?l=openbsd-ports&m=154250517226370&w=2
https://marc.info/?l=openbsd-ports&m=154269346520288&w=2
https://marc.info/?l=openbsd-ports&m=153990734713078&w=2
https://marc.info/?l=openbsd-ports&m=153713104304464&w=2
On 11/15/18 10:19 AM, Stuart Henderson wrote:
On 2018/11/15 09:58, Edward Lopez-Acosta wrote:
Daniel your update builds and runs fine for me on amd64.
Two notes though:
Current version is now 3.7.1, I tested and same patches apply to this
version.
Second is if we have side by side installs then /usr/local/bin/python3
should be a symlink to the users preferred version. Not owned by a package,
same for pip. We can likely solve this by a post install message for the
user.
With the current setup some scripts rely on "#!/usr/bin/env python3" working
and in that case /usr/local/bin/python3 *has* to be owned by the package,
otherwise dependencies on python libraries get messed up.
Unless there's a *very* good reason not to I'd recommend replacing 3.6 with
3.7 rather than having the two in parallel.
