[issue5342] packaging: add tests for old versions cleanup on update
Sergio Callegari added the comment: Getting bitten by this with numpy/scipy installations Having previous scipy installed, pip install -I scipy creates a broken scipy installation, because the previous one is not removed and gets overwritten. For instance, an old spectral.so file leftover hides the spectral.py file from the new installation causing broken behavior. Similarly trying pip uninstall scipy pip install scipy does the same, because the distutils uninstall does not uninistall anything, leaves the scipy directory there and all cheerful ends with a 'Successfully uninstalled scipy'. This is *dangerous*. Mixing old and new code could lead to the weirdest behavior. In principle, one could even use this property to craft packages such that when two subsequent versions are installed one on top of the other malicious things happen even if individually each version is innoquous. -- nosy: +Sergio.Callegari ___ Python tracker <http://bugs.python.org/issue5342> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17419] bdist_wininst installer should allow install in user directory
New submission from Sergio Callegari: When installing a package by calling setup you have a --user option to install the package for a single user in his disk area. E.g., python setup.py install --user A similar possibility should be offered via the windows installer An exe created by python setup.py bdist_wininst when run should offer a tickbox to install in the user disk area rather than globally. -- messages: 184171 nosy: Sergio.Callegari priority: normal severity: normal status: open title: bdist_wininst installer should allow install in user directory versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue17419> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17420] bdist_wininst does not play well with unicode descriptions
New submission from Sergio Callegari: When creating an installer with bdist_wininst, any unicode characters in the description and long_description fields get mangled when running the installer. -- messages: 184172 nosy: Sergio.Callegari priority: normal severity: normal status: open title: bdist_wininst does not play well with unicode descriptions versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue17420> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17420] bdist_wininst does not play well with unicode descriptions
Sergio Callegari added the comment: On 14/03/2013 18:15, Martin v. Löwis wrote: > Martin v. Löwis added the comment: > > Would you like to work on a patch? > > -- > nosy: +loewis > > ___ > Python tracker > <http://bugs.python.org/issue17420> > ___ I'd like to, but I really have no clue on bdist_wininst since I develop on Linux and only occasionally I need to package something so that it can be installed in Win. In my linux machine which is ubuntu based bdist_ininst does not even work since some piece of it is apparently not installed in debian :-( Sergio -- ___ Python tracker <http://bugs.python.org/issue17420> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
