Re: mypy and typeshed
On Thu, Sep 23, 2021 at 5:51 AM Stuart Prescott wrote: > Hi Michael > Hello Stuart, > thanks for uploading the new version of mypy :) > You are welcome! > > With the new mypy, it seems one needs a "pip install types-foo" for just > about > everything before it is able to usefully analyse code. I see #994830 for > python-types-dataclasses, and we have python3-types-toml plus > python3-types- > typed-ast. > > Are you already working towards packaging more of the split off typeshed, > or > do we need a bit more of a team effort on this? > Good question; my answer is a question for you and the Debian Python Team: 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. 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! P.S. From the [A] perspective python-types-dataclasses is not needed as that is a backport for Python <= 3.5 so I'm working with the maintainer of typedload at https://github.com/ltworf/typedload/pull/229 to fix that need so that mypy 0.910 is unblocked from moving to Debian Testing. Cheers,
Re: Python louvain packages naming confusion.
On Tue, 9 Feb 2021 at 23:53, Diane Trout wrote: > Hello, > > The fairly popular (in the world of bioinformatics) ScanPy package uses > a Python version of the louvain clustering algorithm implemented by: > > https://github.com/vtraag/louvain-igraph > https://pypi.org/project/louvain/ > > which installs into the "louvain" dist-packages directory. > (from debc) > ./usr/lib/python3/dist-packages/louvain/ > > I have it mostly packaged > > However currently in the Debian archive there's a different louvain > package > > https://github.com/taynaud/python-louvain > https://pypi.org/project/python-louvain/ > https://salsa.debian.org/python-team/packages/python-louvain > > It installs into (according to debc) > ./usr/lib/python3/dist-packages/community/ > > Unfortunately for this package we now automatically run autodep8 which > fails because the import name is community and not louvain. > In the short term I recommend fixing this by adding a file to the Debian python-louvain package named "debian/tests/autopkgtest-pkg-python.conf" with the contents "import_name = community" -- Michael R. Crusoe
Re: Access to python-team/modules (was RFS: ruamel.yaml.clib)
On Mon, Jun 8, 2020 at 10:51 AM Ondrej Novy wrote: > Hi, > > ne 7. 6. 2020 v 11:26 odesílatel Michael R. Crusoe > napsal: > >> Pardon me, I left out a component of my application for team membership: >> >> I have read >> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst >> and I accept the policy. >> >> On Sun, Jun 7, 2020 at 10:50 AM Michael R. Crusoe wrote: >> >>> Looks like I emailed the wrong mailing list back in March. >>> >>> I'm a DD now, so I don't need sponsorship. Can I have access to move my >>> repository to https://salsa.debian.org/python-team/modules/ ? >>> >> > welcome to the team :) > Thanks!
Re: Access to python-team/modules (was RFS: ruamel.yaml.clib)
Pardon me, I left out a component of my application for team membership:
I have read
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
and I accept the policy.
On Sun, Jun 7, 2020 at 10:50 AM Michael R. Crusoe mailto:cru...@asu.edu>> wrote:
Looks like I emailed the wrong mailing list back in March.
I'm a DD now, so I don't need sponsorship. Can I have access to move
my repository to https://salsa.debian.org/python-team/modules/ ?
My salsa username is crusoe
I would be happy to move some python libraries from the Debian Med
team over to the DPMT:
- https://tracker.debian.org/pkg/python-bz2file
- https://tracker.debian.org/pkg/python3-typed-ast
- https://tracker.debian.org/pkg/python-typing-extensions
- https://tracker.debian.org/pkg/python-schema-salad
- https://tracker.debian.org/pkg/python-rdflib-jsonld
- https://tracker.debian.org/pkg/python-mypy-extensions
And https://tracker.debian.org/pkg/mypy should probably be moved
into the PAPT
Thanks!
-- Forwarded message -
From: *Michael Crusoe* mailto:michael.cru...@gmail.com>>
Date: Sun, Mar 29, 2020 at 2:09 PM
Subject: RFS: ruamel.yaml.clib
To: Debian Python Modules Team
mailto:python-modules-t...@lists.alioth.debian.org>>
Hello,
While looking at updating ruaml.yaml I discovered that the recent
releases need a separate package: ruamel.yaml.clib
gbp clone g...@salsa.debian.org:misterc-guest/ruamel.yaml.clib.git
Please push this to
https://salsa.debian.org/python-team/modules/ruamel.yaml.clib (I
lack the necessary permissions)
My packaging of the newer ruamel.yaml version is at
https://salsa.debian.org/misterc-guest/ruamel.yaml (again, I lack
permissions to push my changes to
https://salsa.debian.org/python-team/modules/ruamel.yaml )
Thanks,
--
Michael R. Crusoe
signature.asc
Description: OpenPGP digital signature
Access to python-team/modules (was RFS: ruamel.yaml.clib)
Looks like I emailed the wrong mailing list back in March. I'm a DD now, so I don't need sponsorship. Can I have access to move my repository to https://salsa.debian.org/python-team/modules/ ? My salsa username is crusoe I would be happy to move some python libraries from the Debian Med team over to the DPMT: - https://tracker.debian.org/pkg/python-bz2file - https://tracker.debian.org/pkg/python3-typed-ast - https://tracker.debian.org/pkg/python-typing-extensions - https://tracker.debian.org/pkg/python-schema-salad - https://tracker.debian.org/pkg/python-rdflib-jsonld - https://tracker.debian.org/pkg/python-mypy-extensions And https://tracker.debian.org/pkg/mypy should probably be moved into the PAPT Thanks! -- Forwarded message - From: Michael Crusoe Date: Sun, Mar 29, 2020 at 2:09 PM Subject: RFS: ruamel.yaml.clib To: Debian Python Modules Team Hello, While looking at updating ruaml.yaml I discovered that the recent releases need a separate package: ruamel.yaml.clib gbp clone g...@salsa.debian.org:misterc-guest/ruamel.yaml.clib.git Please push this to https://salsa.debian.org/python-team/modules/ruamel.yaml.clib (I lack the necessary permissions) My packaging of the newer ruamel.yaml version is at https://salsa.debian.org/misterc-guest/ruamel.yaml (again, I lack permissions to push my changes to https://salsa.debian.org/python-team/modules/ruamel.yaml ) Thanks, -- Michael R. Crusoe
