Nov-05-2017, 03:15 PM
(Nov-05-2017, 02:16 PM)ineedastupidusername Wrote: Say packageA requires scipy version 1.0 and packageB requires scipy versioni 1.1.This typically is not a problem since most packages are backward compatible, if only within the major version. The best thing you can do (at least I do) is to run
pip list --outdated
from the command line. This lists any outdated modules. If there are any, simply run pip install --upgrade package_name
There are three main things to keep in mind with Windows vs Linux, Mac and *nix.
- Windows does not, by default, support utf-8, it uses code pages (what unicode Windows does use is utf-16)
- Windows does not come with a compiler pre-installed.
- Windows does not rely on Python...at all
Item 2 is resolved (in many cases) by the https://www.lfd.uci.edu/~gohlke/pythonlibs/ web site, which has helped the Windows community a great service by pre-compiling many of the third party library's, like 'scipy'.
Item 3 means you can install and uninstall Python as often as you like, and it will not affect the operating system.
Simply trying to copy and paste a bunch of files into a directory would create a nightmare situation, the likes of which the world has never seen.
Quote:If not, your package becomes obscure and nobody uses it
You're right. If you are the publisher of a library, and you do not maintain it and ensure that it complies with the current standards, it will indeed become obscure. That has nothing to do with a 'monopoly' by pip.
If it ain't broke, I just haven't gotten to it yet.
OS: Windows 10, openSuse 42.3, freeBSD 11, Raspian "Stretch"
Python 3.6.5, IDE: PyCharm 2018 Community Edition
OS: Windows 10, openSuse 42.3, freeBSD 11, Raspian "Stretch"
Python 3.6.5, IDE: PyCharm 2018 Community Edition