On Thu, Sep 23, 2021 at 09:25:26AM +0200, Michael R. Crusoe wrote:
> Do we package mypy to [A] support other packages, or are we trying to [B]
> deliver a "complete" offline developer experience? (even if that means
> shipping type hints for python packages not in Debian)
>
> If the goal is [A], then we should stick to the add-hoc approach:
> "python-types-*" packages will only be made as needed for building other
> Debian source packages in our archives. In this instance, developers using
> the packaged version of mypy can use `mypy --install-types' to pull down
> the packages they need from PyPI to their local system/virtualenv.
>
> http://mypy-lang.blogspot.com/2021/06/mypy-0900-released.html
>
> If the goal is [B], then we need to be comprehensive.
Particularly, I try to develop all my Python work against Debian, and
having a mypy that is broken by default without installing stuff that is
not in the Debian archive is a major incovenience.
> Either way we choose, updates to these type hints may need to be made (and
> patches applied) to match the versions of the Python packages in the
> archive (if they have fallen behind or ahead of what is in the typeshed
> repository).
>
>
> > Does it make sense for Debian to package snapshots of all of typeshed in
> > one
> > binary package to save a proliferation of small python-types-foo packages?
> >
>
> Hmm.. a joint source package makes sense (and might save the FTP team from
> reviewing 103 additional submissions), but as each "types-*" package in
> PyPI has its own public version it would be weird to not match their
> versions at all.
>
> Though I guess the monolithic package could have a very long "Provides"
> line mentioning all the components and their versions.
>
> The Copyright file will be interesting! For the two "python-types-*"
> packages I created by hand, I had to dig up the author information from the
> git history at the urging of the FTP gatekeepers :-)
>
> Personally I'm more of an [A] person (out of laziness), but I won't block
> the [B] approach if there is sufficient interest that it doesn't primarily
> fall on my shoulders.
>
> Feedback from the wider Debian Python community is welcome!
Maybe I didn't dedicate enough time for this, but I couldn't figure out
how the pypi packages are produced from the git repository. Knowing this
would help creating such typeshed package by means of some scripting
(not necessarily volunteering, will be happy if someone beats me to it).
signature.asc
Description: PGP signature
