Re: versioned .so files (over in python-dev)

2010-06-24 Thread Barry Warsaw
On Jun 24, 2010, at 11:58 PM, Jakub Wilk wrote:

>What's the point in making distutils produce versioned .so? Such a change is
>going to break lots of packages for exactly zero benefit:

Why so?

>helper tools will need to do unversioned->versioned renames anyway, in order
>to handle non-distutils build systems.

Such helper tools will still need to know what versioned names Python will
import.  Having it in distutils will make the common case easy.  It does
indicate that external tools will need to know what names a particular Python
build supports.  It probably shouldn't be hardcoded.

-Barry



signature.asc
Description: PGP signature


Re: versioned .so files (over in python-dev)

2010-06-24 Thread Jakub Wilk

* Barry Warsaw , 2010-06-24, 17:31:
For those of you not closely following python-dev, I've made a proposal 
for versioned .so file naming for Python 3.2.  It would allow us to 
place extension module .so files for different Python versions (or 
really, Python builds, e.g. 3.2/3.3, debug, UCS2/4, etc) in the same 
directory without naming collisions.


The thread starts here:

http://mail.python.org/pipermail/python-dev/2010-June/100998.html

Except as it specifically impacts Debian, it's probably best to comment 
on the proposal over in python-dev.


What's the point in making distutils produce versioned .so? Such a 
change is going to break lots of packages for exactly zero benefit: 
helper tools will need to do unversioned->versioned renames anyway,

in order to handle non-distutils build systems.

--
Jakub Wilk


signature.asc
Description: Digital signature


versioned .so files (over in python-dev)

2010-06-24 Thread Barry Warsaw
For those of you not closely following python-dev, I've made a proposal for
versioned .so file naming for Python 3.2.  It would allow us to place
extension module .so files for different Python versions (or really, Python
builds, e.g. 3.2/3.3, debug, UCS2/4, etc) in the same directory without naming
collisions.

The thread starts here:

http://mail.python.org/pipermail/python-dev/2010-June/100998.html

Except as it specifically impacts Debian, it's probably best to comment on the
proposal over in python-dev.

-Barry


signature.asc
Description: PGP signature