Message 39179 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	smurf
Recipients
Date	2002-03-19.15:13:46
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
Logged In: YES user_id=10327 A SOVERSION of 0.0 makes perfect sense for the CVS head. Release versions should probably use 1.0. I don't quite know, though, if builds from CVS should keep a fixed SOVERSION -- after all, the API can change. One idea would be to use the tip version number of Doc/api/api.tex, i.e. libpython2.3.so.0.154 or libpython2.3.154.so.0.0. That way, installing a newer CVS version won't instantly beak everything people have built with it.

Logged In: YES 
user_id=10327

A SOVERSION of 0.0 makes perfect sense for the CVS head.

Release versions should probably use 1.0.

I don't quite know, though, if builds from CVS should keep a fixed SOVERSION -- after all, the API can change. One idea would be to use the tip version number of Doc/api/api.tex, i.e. libpython2.3.so.0.154 or libpython2.3.154.so.0.0.
That way, installing a newer CVS version won't instantly beak everything people have built with it.

History
Date	User	Action	Args
2007-08-23 15:11:29	admin	link	issue527027 messages
2007-08-23 15:11:29	admin	create