pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Python hier question



On Tuesday, March 19, 2024 4:40:21 PM CET tlaronde%kergis.com@localhost wrote:
> On Tue, Mar 19, 2024 at 03:40:23PM +0100, Joerg Sonnenberger wrote:
> > On Tuesday, March 19, 2024 8:53:23 AM CET tlaronde%kergis.com@localhost wrote:
> > > What is the purpose of prefixing the installation path with the
> > > exact version of the interpreter?
> > 
> > 20+ years of history of incompatibilities between Python versions,
> > including needing different module versions on older Python versions.
> > Most systems will have only one Python version installed anyway (modulo 2.7),
> > so there isn't anything to be shared. But if you need different versions,
> > a clean split is often much easier, especially when you also need modules
> > that involve C/Rust/whatever extension modules. 
> 
> OK, this is what I suspected (difference between theory and practice).
> 
> But imagining that one has both 2.7 and say 3.11, if xcb bindings were
> to be added (for pkgsrc), will the pkgsrc framework create both 2.7
> and 3.11 subdirs or will only one version of the python interpreter be
> considered? (in this example, the interface requires python >= 2.5, so
> compatible with both)
> 

The package is built and installed for the version of the user requested.
So if they ask for Python 3.10, they get that, if they ask for Python 3.11 (or no
specific version), they get that.

Joerg





Home | Main Index | Thread Index | Old Index