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 prlw1
Recipients prlw1
Date 2013-05-14.14:43:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368542639.2.0.817126483539.issue17975@psf.upfronthosting.co.za>
In-reply-to
Content
I currently have python 2.7 and 3.2 installed concurrently. I just tried to install 3.3 as well, but a file conflicts between 3.2 and 3.3. It is libpython3.so.

Given that we go out of our way e.g. with

$(INSTALL_DATA) Misc/python.pc $(DESTDIR)$(LIBPC)/python-$(VERSION).pc

to avoid clashes, what should be done about PY3LIBRARY?
History
Date User Action Args
2013-05-14 14:43:59prlw1setrecipients: + prlw1
2013-05-14 14:43:59prlw1setmessageid: <1368542639.2.0.817126483539.issue17975@psf.upfronthosting.co.za>
2013-05-14 14:43:59prlw1linkissue17975 messages
2013-05-14 14:43:59prlw1create