Project membership for requirements-language-server

Packaging
1

I create a language server for pip’s requirements.txt files which supports:

  • complete PYPI package names by fetching names from https://pypi.org/ and cache it in a trie
  • complete local package names by pip
  • hover the package information: version/license/requires/…
  • diagnostic for unknown PYPI packages
  • complete keywords for requirements.txt

It will provide convenience for any python packager who are editing requirements.txt

Per PEP 609, any existing PyPA member can propose to accept a project into PyPA, and members vote to decide whether to accept that proposal. Criteria include the project adopting the PyPA’s Code of Conduct and the project being relevant to Python packaging, as determined by existing members of PyPA.

I believe it is relevant to Python packaging and accept CoC of PYPA. Could anyone vote for it? TIA!

2

I think this is a cool idea, but on some level it might not be a good fit for PyPA inclusion:

  • requirements.txt isn’t actually a packaging standard, it’s a pip-specific feature that some other tools support (subsets of) for convenience
  • More specifically it’s arguably a legacy packaging feature, since PEP 751 standardized proper lockfiles and most users should use use pyproject.toml for non-locking resolutions

(OTOH, PyPA has historically been inclusionist, and I don’t speak for anybody except myself :slightly_smiling_face:)

1 Like
3

I agree with William because of PEP 751 where this might not be a fit on some level for PyPA. I think it is a cool idea and maybe it might make sense to combine forces a little bit with GitHub - terror/pyproject: A linter and language server for `pyproject.toml` files · GitHub for a pyproject.toml language server that has some of the cool features you have already for auto completion of project names. I think that would be a good fit for PyPA to have a language server around pyproject.toml, which is a packaging standard.

I also do not speak for anyone but myself here :slight_smile:

4

I agree. This sounds like a cool project, but I don’t think it’s a good fit for PyPA inclusion. But looking at it the other way, what benefit would the project get from being in the PyPA? We don’t actually provide any tangible benefits, if I’m honest :slightly_smiling_face:

1 Like