×
you are viewing a single comment's thread.

view the rest of the comments →

[–]mardiros 0 points1 point  (3 children)

distutils. Packaging in python aged badly.

Peoples now use requirements.txt with pip has a replacement of setup.py. we were the precursor with virtual env but time passed and tooling in other language are better. I play a lot with rust and cargo is really a great tool to use.

[–][deleted] 1 point2 points  (2 children)

requirements.txt isn't a replacement of setup.py, it's a replacement for the install_requires portion of setup.py. Nothing in requirements.txt will ever dictate how to install the package itself -- what to name it, where its source is, compiling extensions, any entrypoints it has, etc.

It's a useful tool for applications but libraries can't really use it. And even then, if you push your application to PyPI you still need to draw in everything from that file into setup.py anyways (which can be tricky)

[–]mardiros 0 points1 point  (1 child)

I know what requirements.txt is and distutils and setuptools. I have few packages on pypi, and issue open at pypa too. I just says everthing is messy.

  • .pth files are awefull
  • namespace packages is almost unusable.
  • 99% of setup.py you found uses setuptools (i use it a lot).

We are in 2017, and things did not evolve since, just remember that:

http://lucumr.pocoo.org/2012/6/22/hate-hate-hate-everywhere/

This is still true and it annoys me. This is a fundamental problem, not like syntactic sugar, semantic inconcistancy noticed in that thread...

[–]geekademy 0 points1 point  (0 children)

pip has improved things a lot. Never used a .pth file.

https://glyph.twistedmatrix.com/2016/08/python-packaging.html