PAPT and DPMT become DPT
PAPT and DPMT become DPT Historically, the Debian Python ecosystem was maintained by two separate teams: the Debian Python Applications Packaging Team (PAPT) for applications, and the Debian Python Modules Team (DPMT) for modules used by applications. As there was substantial overlap between the members of these teams, their work, and their tooling, these teams have been merged into one: the Debian Python Team (DPT). Changes --- This merge mainly affects package maintainers. End users should not see a change beyond the Maintainer field of packages. For maintainers, the following has changed: * The respective PAPT and DPMT policies are superseded by the new, more compact DPT policy [1]. Please take a few minutes to familiarize yourself with this new policy. * All Salsa repositories are in "packages" subgroup [2] now. Please set Vcs-* fields of new packages accordingly. * The Maintainer field of new packages should now be set to "Debian Python Team ". Migration - On Salsa, redirects have been implemented from the old "applications" and "modules" subgroups to the new "packages" subgroup. Vcs-* URLs should continue working for now. But it's still a good idea to update your local git remotes to point to new "packages" subgroup. Maintainer and Vcs-* fields were mass-changed in git repositories so there is nothing you need to do as maintainer of DPMT/PAPT packages. All members of DPMT or PAPT are members of DPT now and have access to "packages" subgroup. As always, new contributors are welcomed :) [1] https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst [2] https://salsa.debian.org/python-team/packages -- Best regards Ondřej Nový signature.asc Description: This is a digitally signed message part
Re: Merging the PAPT and the DMPT
Hi, po 21. 9. 2020 v 13:04 odesílatel Ondrej Novy napsal: > Todo: > >- send debian-devel-announce (i will) >- mass-commit vcs+maintainer change > > done. Thanks to all who helped me with these. -- Best regards Ondřej Nový
Packaging a python module when already using cmake buildsystem
Hi, I'm trying to package a newly added python component of our tool https://tracker.debian.org/pkg/armnn. It has a setup.py and uses SetupTools and DistUtils so I was hoping to add "--with Python3" and hope that a lot of magic would be done by pybuild. However as I'm already using cmake as the build system I can't stick pybuild in there. Do I have to use .pyinstall files to further split my packages and install the python module? Any pointers to relevant docs would be useful, currently going off of: https://www.debian.org/doc/packaging-manuals/python-policy/index.html https://wiki.debian.org/Python/LibraryStyleGuide Thanks, Francis. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Packaging a python module when already using cmake buildsystem
Hi, I'm trying to package a newly added python component of our tool https://tracker.debian.org/pkg/armnn. It has a setup.py and uses SetupTools and DistUtils so I was hoping to add --with Python3 and hope that a lot of magic would be done by pybuild. However as I'm already using cmake as the build system I can't stick pybuild in there. Do I have to use .pyinstall files to further split my packages and install the python module? Any pointers to relevant docs would be useful, currently going off of: https://www.debian.org/doc/packaging-manuals/python-policy/index.html https://wiki.debian.org/Python/LibraryStyleGuide Thanks, Francis. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Re: PAPT: join request
Hi, pá 11. 9. 2020 v 17:25 odesílatel Fred Le Meur < frederic.le-m...@ac-versailles.fr> napsal: > Hello, > > * I want to join Debian Python Team welcome :) -- Best regards Ondřej Nový
Re: Joining the team
Hi, po 14. 9. 2020 v 8:11 odesílatel Chris MacNaughton < chris.macnaugh...@canonical.com> napsal: > Hey team, > > I'm Chris MacNaughton (icey) and I've been working on packaging for > OpenStack in Ubuntu for about six months now and would love to help > contribute upstream a bit. I'm working on a new package that's an > OpenStack dependency now and would prefer to work that more in Debian, > rather than maintaining a separate library in Ubuntu so it seems like a > great time to get in touch! Zigo asked me to see about joining this team > if I'll be working on doing these kinds of things upstream so here I am! > that's cool! Please follow policy how to join team: https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst Thank you. -- Best regards Ondřej Nový
Re: Packaging a python module when already using cmake buildsystem
> It has a setup.py and uses SetupTools and DistUtils so I was hoping to > add --with Python3 and hope that a lot of magic would be done by pybuild. > However as I'm already using cmake as the build system I can't stick > pybuild in there. We use both pybuild and cmake for a couple of SIP packages: https://salsa.debian.org/3dprinting-team/libarcus However, in this case, upstream doesn't provide a setup.py at all, so cmake is used automatically. I do believe that you can force the use of cmake by adding a "--with cmake" - have you tried that?
