News for hackers. Stuff that matters.
Re:Python's New Package Landscape by azag0 on Thursday October 18, 2018 @08:48AM (#18247835)
It is an overkill for pure-python packages or packages with simple C extensions. Conda was developed specifically to handle non-python dependencies, which would be difficult to build in setup.py.

Also, a conda package is not a replacement for a distutils/setuptools package. When building a conda package, one still calls setup.py. So every python conda package has to be a distutils/setuptools package anyway.

Re:Python's New Package Landscape by 131012 on Thursday October 18, 2018 @09:02AM (#18247930)
Thanks for caveat. Nonetheless, anaconda makes my life so much easier when working with python libraries. If anybody got any other reasons to be careful of it, I'm interested!
Re:Python's New Package Landscape by flatfilefan on Thursday October 18, 2018 @09:42AM (#18248207)
If you need to work with cutting-edge python tools (e.g.from GitHub) it’s often easier to use virtualenv to control the versions you need installed.
Re:Python's New Package Landscape by dagw on Thursday October 18, 2018 @09:55AM (#18248318)
conda environments support pip and arbitrary pip commands. So if you use pip to for example install a specific version of a library directly from github that information will be stored in your conda environment and be reproduced every time you recreate your environments.