[issue18493] make profile-opt fails with pre-existing python2.7 in path

Zachary Ware added the comment: This was fixed in 3.x in 2015 and later backported to 2.7 in 2017. Thanks for the report, Claudio, and I'm sorry nobody noticed this earlier or we could have fixed the issue two years earlier! -- nosy: +zach.ware resolution: -> fixed stage: -> resol

[issue18493] make profile-opt fails with pre-existing python2.7 in path

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue18493] make profile-opt fails with pre-existing python2.7 in path

Mark Lawrence added the comment: Can somebody please take a look at the inline patch in msg193313. -- nosy: +BreamoreBoy type: -> behavior versions: +Python 3.4, Python 3.5 ___ Python tracker _

[issue18493] make profile-opt fails with pre-existing python2.7 in path

New submission from Claudio Freire: When building with --enable-shared in an environment that already has a python2.7 (and I'd expect the same to happen to 3.x), make profile-opt fails because it attempts to load the existing libpython instead of the just-built one. run_profile_task should us