3 ms·

The proliferation of requirements.txt is one of the key reasons why Python packaging sucks so much.

• kelipso 3y ago
  Right what we need is a requirements.yaml (better yet, create an entirely new markup language for this particular project) and another new package manager for it. One day (one day!) I will start a project without python. One can hope.
  • starlevel003 3y ago
    > Right what we need is a requirements.yaml It already exists, it's called pyproject.toml. It already existed for years in the form of setup.py. Requirements.txt means that projects can't be automatically installed which contributes massively to the difficulty of getting packages to work.
    • mkesper 3y ago
      Pyproject.toml is a right step afaict but man is it complicated: "Please note that some of these configurations are deprecated, obsolete or at least discouraged, but they are made available to ensure portability." Core vs setuptools-specific etc. See https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html https://setuptools.pypa.io/en/latest/userguide/pyproject_con... and https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ https://packaging.python.org/en/latest/specifications/declar...