Opened 3 years ago
Closed 17 months ago
#63955 closed enhancement (fixed)
ntpsec @1.2.1_1: support Python 3
Reported by: | l2dy (Zero King) | Owned by: | fhgwright (Fred Wright) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | ntpsec |
Description
Python 2 has been discontinued, we should use Python 3 which is supported.
https://gitlab.com/NTPsec/ntpsec/-/blob/NTPsec_1_2_1/INSTALL.adoc
Python 2.x, x >= 6, or Python 3.x, x >= 3
Change History (6)
comment:1 Changed 3 years ago by fhgwright (Fred Wright)
comment:2 Changed 3 years ago by l2dy (Zero King)
On the other hand, this will prevent users willing to upgrade from doing so.
Let's leave this ticket open until Python variants or subports get implemented.
comment:3 Changed 3 years ago by fhgwright (Fred Wright)
Agreed, but it should probably be titled "ntpsec: support Python 3".
I don't have permissions to change the summary, even as the ticket owner. Thank you, Trac. :-)
comment:4 Changed 3 years ago by l2dy (Zero King)
Summary: | ntpsec @1.2.1_1: use Python 3 → ntpsec @1.2.1_1: support Python 3 |
---|
comment:5 Changed 18 months ago by fhgwright (Fred Wright)
I have this implemented, but ran into a small hitch and won't have time to do any more on it until next month.
comment:6 Changed 17 months ago by fhgwright (Fred Wright)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
The
ntpsec
port provides Python modules which can be used by users. Changing the Python version may break users' existing code, and adapting their existing Python 2 code to Python 3 may require serious work, due to the significant incompatibilities between Python 2 and Python 3.The proper fix for this would be to have variants for Python versions (or, better still, multiple subports), but that's significant work. Complicating this is that the upstream method for targeting a different Python version from the one used to run
waf
doesn't seem to work correctly in the MacPorts environment (for as yet undetermined reasons), and the currentwaf
PortGroup doesn't provide a properly functioning method to specify its Python version (thoughwaf
itself is compatible with a wide range of Python versions).