[Diane Trout, 2017-09-21]
> I made larger changes to statsmodels, by using pybuild instead of the
> previous multiple targets in debian/rules.
you can simplify it even further by using pybuild's --ext-dest-dir:
(I didn't test as this branch FTBFS for me)
diff --git a/debian/rules b/debian/rules
i
[James Valleroy, 2017-09-07]
> I would like to join the Debian Python Modules Team. I am working on a
> package for django-axes and would like it to maintain it within the team.
>
> My Alioth login is jvalleroy-guest. I have read
> https://python-modules.alioth.debian.org/policy.html and accept it
> > > I made larger changes to statsmodels, by using pybuild instead of the
> > > previous multiple targets in debian/rules.
> > you can simplify it even further by using pybuild's --ext-dest-dir:
> > (I didn't test as this branch FTBFS for me)
> how recent is that feature?
it's available since th
[drebs, 2017-09-23]
> Hi, I am interested in updating the subliminal[2] package[1]. Is there
> someone else already working on that? If not, what would be the process
> for having it uploaded? (i am not a dm or dd) Should i send the source
> package to this list? Would someone sponsor it? :)
point
[Gregor Riepl, 2017-12-04]
> I tried to follow the guidelines at
> http://python-modules.alioth.debian.org/policy.html closely, and I intend to
> keep doing that for further work on this package (or other Python packages).
>
> My Alioth login is: onitake-guest
welcome in the team! :)
--
GPG: 1D2
Hi,
I plan to prepare new dh-python upload soon and hence a question about
a bit controversial change: should dh_python2 (as we discussed during
last DebConf's Python BoF) replace /usr/bin/python shebangs with
/usr/bin/python2?
Please note that it's not about pointing /usr/bin/python to python3 -
[Michael Hudson-Doyle, 2017-12-19]
> > I want to create a package (pyraf, #711038) for both Python2 and
> > Python3. While the package itself is still not Python 3 compatible,
> > upstream says that running through 2to3 will make it; however the
> > resulting code is not Python 2 compatible anymore
[Andreas Tille, 2018-01-15]
> 1) test suite
>
> I: pybuild base:184: cd
> /build/python-aws-xray-sdk-0.95/.pybuild/pythonX.Y_2.7/build; python2.7 -m
> pytest tests
> = test session starts
> ==
> platform linux2 -- Python 2.7.14+, pytest-
[Andreas Tille, 2018-01-15]
> Now I need to exclude those tests that try to access remote network
> locations but I failed with the same method as you proposed above.
>
> Any clue how I can do that properly (please Git pull to see my failed
> attempts).
if you want to disable specific test (not t
[Alexandros Afentoulis, 2018-01-21]
> This is the test, essentially two HTTP endpoints where a GET to the
> first results in a GET to the second, as far as I can tell:
pybuild (by default) sets http{,s}_proxy to http{,s}://127.0.0.1:9/
in addition to setting easy_install's allow_hosts to None
To
[Andreas Tille, 2018-01-22]
> Hi,
>
> I kept on working packaging python-moto predependencies. I'm now
> stumbling upon python-backports.tempfile[1] and
> python-backports.weakref[2]. My naive packaging attempt puts
> the modules into
>
>/usr/lib/python*/dist-packages/backports
>
> leaving
[eamanu15 ., 2018-01-18]
> I send this mail requesting join to the team for many reason. Fist, I love
> Python, I use it on my job and for my hobbies. Second, I am new on Debian,
> so I am enthusiastic about learn to work collaboratily in a open source.
> Furthermore I am maintainer of cligh, a pyt
> > > However, in Debian case, I do not know how this can be handled as
> > > 2 packages cannot hold the same file (even if __init__ is only an empty
> > > file), and at least one must be present (if you install only one).
>
> The Python jargon is that the "backports" shared by backports.tempfile
> >My personal intepretation is that since this package is not used as
> >python library this should be "fontmake" single package, but we need
> >someone from Python Teams to confirm that.
>
> I think that makes sense.
>
> You have to make a judgement call about the primary purpose of the
> packa
[Paul Wise, 2018-01-28]
> On Sun, Jan 28, 2018 at 2:30 AM, Piotr Ożarowski wrote:
>
> > please also remember to install this private library into private (as
> > in: outside dist-packages) dir. You can do that with something like:
>
> Is there or should there be a lintia
[Aggelos Avgerinos, 2018-01-30]
> I would like to join the DPMT to maintain py-radix within the team, also
> planning to adopt more packages in the future.
> I'm currently sponsored by Apollon OIkonomopoilos (apoikos)
>
> My alioth login is avgerinos-guest
>
> I have read the team's policy
> (htt
[W. Martin Borgert, 2018-02-07]
> how about moving the Python team(s) to salsa?
that's the natural place to move from alioth for both teams.
PAPT's repos will also have to be converted from svn to git.
All we need is a volunteer who will prepare it and supervise the
process.
> And how about mergi
[Ole Streicher, 2018-02-07]
> Piotr Ożarowski writes:
> > [W. Martin Borgert, 2018-02-07]
> >> And how about merging the modules and apps teams into one?
> >
> > I don't understand this, though. Why you want to merge them?
> > Sure, packaging Python
Hi,
Thanks for pushing it forward
[Ondrej Novy, 2018-02-08]
> I created team "python-team" in salsa with 3 subgroups:
> interpreter
> modules
> packages
could you describe these groups? What goes into modules and what into
packages?
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Hi Andreas,
[Andreas Tille, 2018-02-12]
> On Wed, Feb 07, 2018 at 10:29:37AM +0100, Piotr Ożarowski wrote:
> > > And how about merging the modules and apps teams into one?
> > If not separated at team level, I definitely want to have them somehow
> > separated at repos
> python-bd2k[1] which builds fine
it doesn't if you remove the override to not run Python 3.X tests
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Scott Talbert, 2018-02-13]
> > > I would like to join DPMT so that I could maintain the
> > > python-pytest-xdist package (that I've recently discussed adopting
> > > with Daniel Stender). Additionally, I'll need to package a new
> > > dependency for a new upstream release of python-pytest-xdist.
[W. Martin Borgert, 2018-02-14]
> if I have a Python program, that currently is not yet maintained
> by PAPT, but want to move it to the team: May I use
> salsa.d.o/python-team/applications/ now? Any objections?
yes. Please wait until the workflow is selected
--
GPG: 1D2F A898 58DA AF62 1786 2DF7
[Ole Streicher, 2018-03-20]
> test-python%:
> HOME=/tmp/ PYTHONPATH=$(CURDIR)/.pybuild/pythonX.Y_$*/build python$*
> debian/tests/pyraf-test.py
>
> override_dh_auto_test: $(PYTHON2:%=test-python%) $(PYTHON3:%=test-python%)
>
> This however does not work anymore, since the subdir under .p
Hi,
Here's a list of packages that will FTBFS soon if dh-python will not be
added to Build-Depends (it's time to drop dh-python from python3's
Depends and old version of dh_python2 from python package).
http://people.debian.org/~piotr/dh_python3_without_dh-python.list
http://people.debian.org/~pi
[ChangZhuo Chen (陳昌倬), 2018-02-13]
> I would like to request to join Python Application Packaging Team for
> some packages I maintain (e.g. cppman, ctop, pydocstyle, ...)
>
> My salsa account is czchen.
you're in. Sorry for the delay
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
> My alioth account is: arkadefr-guest
please create an account on salsa.d.o and point me to it if you're still
interested (and sorry for the delay)
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Joseph Herlant, 2018-02-15]
> I'm one of the maintainers of pylint-django, pylint-plugin-utils and asciidoc.
> I'd like to be added to the DPMT team for the 2 first repos and I'd
> like to move asciidoc to PAPT (it is EOL but it will take a few months
> for me to take care of its EOL properly).
>
Hi,
[Moritz Schlarb, 2018-02-15]
> please also add my user "moschlar-guest" to the respective Groups on Salsa.
looks like my thread is broken, I cannot find referenced emails. Do you
accept our policy? Which packages do you want to work on?
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 76
[Michal Arbet, 2018-02-15]
> Could you please add me to DPMT team ?
>
> Why do I want to join a team ?
> Now I am part of Openstack-team and there was discussed that many python
> packages will be moved to DPMT team , so I want to continue with
> contributing to Openstack via DPMT team.
>
> What
[Dominik George, 2018-02-22]
> please add me to the team(s) on Salsa. I am an existing DPMT member.
>
> Username: natureshadow-guest
I added the one without "-guest" on salsa. Congrats :)_
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Hideki Yamane, 2018-02-24]
> I'd like to put sphinx-intl package(*) under DPMT umbrella, so could
> you add me your group on salsa, please?
done, welcome :)
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Andre Bianchi, 2018-02-28]
> Hello! I'd like to join DPMT to help maintaining packages related to
> Weblate. I'm currently working on python3-openid and
> python-social-auth-core, and plan to tackle all others that are
> deps to Weblate.
>
> My logins in alioth and salsa are: drebs-guest
>
> I h
[Robin Jarry, 2018-02-27]
> after some discussions on https://bugs.debian.org/883529, Martin Borgert
> suggested that buildbot becomes maintained by the Python Applications
> Packaging Team.
>
> That sounds like a good thing to have more than one person able to work
> on this package.
>
> I am cu
[Christophe Siraut, 2018-03-01]
> I have prepared an update for python-jsontest (#840033), I'd like to
> push it on salsa and hereby request membership to DPMT group, my
> username is tobald. Can you check my svn access for python-apps as well?
>
> I have read and agree to the terms of the team po
[Ana C. Custura, 2018-03-06]
> I am writing about joining the DPMT. I have a handful of prospective
> python packages which I would like to maintain within the team, and
> some existing ones to transition.
> I have read and accepted the policy at
> https://python-modules.alioth.debian.org/policy.
[Julien Muchembled, 2018-03-08]
> My username on salsa on jmuchemb-guest. I'm already member of DPMT.
>
> I saw this answer on this ML but I don't see this link:
>
> Le 02/14/18 à 21:46, Jonathan Carter (highvoltage) a écrit :
> > I think you have to click on 'request access' on
> > https://salsa
[Adrian Vondendriesch, 2018-03-08]
> please add me to the DPMT group on salsa.debian.org. I'm already a
> member of the DPMT. My username is discostu-guest.
done :)
> Unfortunately the web interface doesn't show any "Request Access"
> button.
that's great news! (I hated that button on alioth!)
-
[Lev Lamberov, 2018-03-12]
> I'd like to join DPMT, Debian Python Modules Team. The motivation is
> that I'd like to package and maintain several Python modules within the
> team. Namely, sexpdata [1] and epc [2], which are dependencies for
> emacs-jedi [3].
jedi maintainer (including vim-python-j
[Craig Small, 2018-03-14]
> Hello,
> As I'm looking at maintaining two python modules (pytest-vcr and
> mastodon) I'm asking to join the DPMT. My salsa login is csmall, I have
> read and accept the python module policy. I'm a Debian developer so
> probably don't need an ACL change.
I added you
[Aggelos Avgerinos, 2018-03-16]
> It's been a long time, so I'm re-pinging you again:
done, sorry for the delay
> On 14/02/2018 10:39, Aggelos Avgerinos wrote:
> > Hello again,
> >
> > Thanks for accepting in to the DPMT on alioth.
> >
> > Can you please do the same for salsa? (avgerinos-guest)
>
[Dima Kogan, 2018-03-17]
> Hi. I'd like to join the DPMT team to package and upload some modules.
>
> Salsa username: dkogan
do you accept our policy?
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Yago González, 2018-03-19]
> Recently I started maintaining the "python-tabulate" package, and would
> like to join the team to be able to update the Git repository in Salsa,
> as well as being able to help with other Python packages in the future.
>
> I acknowledge reading the team's policy. Her
[Ole Streicher, 2018-03-24]
> I am currently rewriting part of the blends-dev package which is used
> for maintaining Debian Pure Blends into Python. This however comes out
> some abstractions of Blends (namely the tasks infrastructure) that may
> be re-usable on other places, f.e. in the blends.d.
[Pierre-Elliott Bécue, 2018-03-18]
> After hanging around a lot in DPMT, I'm currently packaging an app that
> henceforth would definitely find its place into PAPT namespace on salsa.
>
> I'll commit myself to follow the PAPT policy. :)
>
> My salsa login is peb-guest
you're in, welcome :)
--
G
[Georg Faerber, 2018-03-15]
> I would like to join the team.
>
> I'm intending to package mwic [1], Misspelled Words In Context, which is
> a spell-checker that groups possible misspellings and shows them in
> their contexts. This is useful for checking technical documents that
> often contain wor
> > [Moritz Schlarb, 2018-02-15]
> > > please also add my user "moschlar-guest" to the respective Groups on
> > > Salsa.
done :)
> Original email: https://lists.debian.org/debian-python/2017/01/msg00030.html
>
> So it's about the "nagstamon" package.
thanks Raphaël
--
GPG: 1D2F A898 58DA AF62
[Matthias Klose, 2018-03-27]
> On 26.03.2018 19:32, Piotr Ożarowski wrote:
> > Hi,
> >
> > Here's a list of packages that will FTBFS soon if dh-python will not be
> > added to Build-Depends (it's time to drop dh-python from python3's
> > Depends a
[Matthias Klose, 2018-03-27]
> yes. please see below for a description of such packages. Or you might share
> the
> approach how you did construct those lists you posted.
I used codesearch.d.n¹, then downloaded JSON representation of that
search² and removed all packages that Build-Depend on dh-p
[Andreas Tille, 2018-04-05]
> Traceback (most recent call last):
> File "setup.py", line 435, in
> readme_rst = handle.read()
> File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
> return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't
[T K Sourabh, 2018-03-28]
> I am interested in contributing to python modules for Debian. Happy to help.
>
> Why you want to join the team:
> I want to help in contributing to packaging python module.
>
> Your Alioth login:
> sourabhtk37-guest
>
> I have read https://python-modules.alioth.debian
[Andreas Tille, 2018-03-28]
> I failed to find a button to ask for membership in the Salsa web
let me know if you find it (bonus points for also letting me know how to
disable it)
> interface for DPMT. Please add me since I contributed to some python-*
> packages in the past and would like to ke
Hi Nikolaus,
[Nikolaus Rath, 2018-04-03]
> Could someone please add me to the DPMT and DPAP teams on Salsa? My
> Alioth and Salsa username is nikratio-guest.
what do you think about our policy and on which packages do you want to
work with us?
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745
[Andreas Tille, 2018-04-05]
> On Thu, Apr 05, 2018 at 04:40:44PM +0200, Piotr Ożarowski wrote:
> > [Andreas Tille, 2018-03-28]
> > > I failed to find a button to ask for membership in the Salsa web
> >
> > let me know if you find it (bonus points for also letting
[Nikolaus Rath, 2018-04-05]
> Huh? I have been member of the team for a few years already, I'm just
> not registered on Salsa yet (as far as I know Alioth memberships don't
> transfer automatically).
ah, sorry, I didn't check alioth. You're now also a member on salsa.
BTW, there's no need to send
Hi,
We don't have a procedure to select a new admin (or terms / rotations
unfortunately) so if you want to blame current admins for this, Ondřej
Nový will share the blame now :)
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
signature.asc
Description: PGP signature
[Peter Cock, 2018-04-06]
> Piotr, I think your fix would be worth including in Biopython.
>
> Do you want to submit this as a pull request, or give me
> permission to do so by email?
go ahead
> We'd need you to agree to both the Biopython License Agreement
> and the 3-clause BSD licence, and say
[florian grignon, 2018-03-28]
> I would like to join DPMT.
>
> I'm maintaining one python package that I would like to team maintain
> (python3-anosql). For this goal, I'd like also to join the DPMT salsa group
> to move the git repository to the DPMT salsa group.
>
> My alioth and salsa login ar
[Ghislain Vaillant, 2018-04-09]
> > I realised that upstream of tifffile[1] switched to Python3. When
> > inspecting the package I somehow think that its main purpose is rather a
> > user application than a Python module and thus I would rather rename the
> > binary from python-tifffile to tifffil
[Julien Puydt, 2018-04-11]
> I'm already part of the teams, but as jpuydt-guest, and I would
> now need to be part of the same teams as jpuydt, as I just completed the
> process to become a DD.
congratulations :)
> If I remember well, I'm part of:
right (https://alioth.debian.org/users/jpuydt-gu
[Andreas Tille, 2018-04-26]
> some packages I maintain received this kind of bug in the case of
> python-skbio it is
>
>ModuleNotFoundError: No module named 'skbio'
>
> So the module that was just build is not found. I guess this is due to
> some misuse of pybuild - but what did I wrong? Py
[Andreas Tille, 2018-04-30]
> > PYTHONPATH=$(shell pybuild --print build_dir --interpreter python3) ...
>
> This worked nicely for python-skbio.
>
> > I fixed few packages already, here's a list of other affected ones:
> > ...
> > snakemake Debian Med Packaging Team
>
> I tried the same
[Andreas Tille, 2018-04-30]
> On Mon, Apr 30, 2018 at 03:57:51PM +0200, Piotr Ożarowski wrote:
> > [Andreas Tille, 2018-04-30]
> > > > PYTHONPATH=$(shell pybuild --print build_dir --interpreter python3) ...
> > > I tried the same trick for snakemake in Git[1] but fai
[Ole Streicher, 2018-05-16]
> # This module includes files automatically generated from ply (these end in
> # _lextab.py and _parsetab.py). To generate these files, remove them from this
> # folder, then build astropy and run the tests in-place:
> #
> # python setup.py build_ext --inplace
if it'
[Matthias Klose, 2018-05-17]
> PEP 394 [1] saw an update in April 2018 [2], the diffs at [3].
>
> The most important change from my point of view is
>
> -* It is suggested that even distribution-specific packages follow the
> - ``python2``/``python3`` convention, even in code that is not intende
> who said, that we should rename packages? The only packages being dropped are
> the python defaults packages.
> >
> > I refuse to do that work!
>
> There is no work in renaming the packages. It's about the dependency
> generation
> and the shebang.
the work in dh-python is not trivial. The wo
> A bit disappointed about this style of communication, Matthias
same here (you want us to do something without explaining reasons)
EOT for me.
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Víctor Cuadrado Juan, 2018-05-17]
> > I maintain some packages in DPMT, such as:
> > https://salsa.debian.org/python-team/modules/python3-proselint
> > https://salsa.debian.org/python-team/modules/python-neovim
> > and I wanted to push changes to them.
> >
> > Could somebody add me to the followi
> > I'm the maintainer[1] of the quodlibet[2] package. I'd like to join the
> > team. Thanks to W. Martin Borgert (debacle), the repo is there already.
> > I still need permissions to push, though).
>
> what is your salsa username please?
It's cargill-guest. Now in the team, welcome :)
--
GPG: 1
[Willem van den Akker, 2018-05-31]
> I am maintaining python-ldap and want to make it a team-package.
> My login name: wvdakker-guest
> I have read and accept the Debian Python Modules Team - Policy on
> salso (there is in invalid link to alioth in the document).
>
> A 3.10 package is available o
[Matthias Klose, 2018-06-08]
> from my point of view this doesn't address:
>
> - being able to de-install the python command for buster, if
>people don't use it. Most dependencies are auto-generated, so
>these could be replaced by dependencies on python2. I would
>assume that the maj
[Dima Kogan, 2018-06-18]
> Yes. I accept the policy. Sorry, I wasn't subscribed to the list, and
> never saw this reply.
welcome :)
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Alexander Gerasiov, 2018-06-20]
> I'd like to join the team as I need to debianize some python modules
> for internal project and would like to upload them into archive too.
>
> I think it would be best to maintain them under DPMT.
>
> And of course I've read and accept team policy for package m
[Stuart Prescott, 2018-06-26]
> > # ls -l /build/snakemake-5.1.5/.pybuild
> > total 8
> > drwxr-xr-x 3 pbuilder pbuilder 4096 Jun 26 09:20 cpython3_3.6
> > drwxr-xr-x 3 pbuilder pbuilder 4096 Jun 26 09:20 cpython3_3.6_snakemake
> >
> > and the latter contains all the installed files while the form
[Piotr Ożarowski, 2018-06-27]
> [Stuart Prescott, 2018-06-26]
> > > # ls -l /build/snakemake-5.1.5/.pybuild
> > > total 8
> > > drwxr-xr-x 3 pbuilder pbuilder 4096 Jun 26 09:20 cpython3_3.6
> > > drwxr-xr-x 3 pbuilder pbuilder 4096 Jun 26 09:20 cpython3_3.
[Elena ``of Valhalla'', 2018-06-30]
> I was already a (not very active) member of PAPT, where I maintain
> pdfposter, and I would like to have access to it on salsa, where my
> username is valhalla.
done :)
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Martin Kelly, 2018-07-15]
> I would like to join the Salsa Python Modules team in order to continue
> maintaining my package python-gmpy2. I previously had Alioth access and have
> finally had time to migrate to Salsa.
>
> My Salsa login is aomighty-guest.
done
--
GPG: 1D2F A898 58DA AF62 1786
[Ben Finney, 2018-07-15]
> The Debian package ‘gandi-cli’ is building with none of the Python
> library dependencies detected, so the “Depends” field contains none of
> the required Python library packages. Why isn't ‘dh_python3’ reading the
> dependencies from ‘requires.txt’?
gandi-cli name sugge
[Ben Finney, 2018-07-15]
> Which particular of those files are right or wrong, according to the
> Debian Python Policy §2.5?
>
> * usr/lib/python3.7/dist-packages/coverage-4.5.1.egg-info/
> * usr/lib/python3/dist-packages/coverage-4.5.1.egg-info/
> * usr/lib/python3.7/dist-packages/coverage-4.5.1.
[Dean Serenevy, 2018-07-18]
> Hello, I am a user of the python3-kivy package and just noticed that
> kivy is no longer listed in buster [1].
>
> Is help needed? (I am not a DD, but I am willing to test and submit
> packaging patches if it would help.)
tracker¹ points to bug #873501² (FTBFS with c
Hi Felix,
[Felix Lechner, 2018-07-16]
> I would like to join the PAPT team, please. Any pointers would be
> appreciated. Thank you!
let us know your salsa.d.o username if you accept our policy
https://salsa.debian.org/python-team/tools/python-apps/blob/master/policy.rst
--
GPG: 1D2F A898 58DA AF
[PICCA Frederic-Emmanuel, 2018-08-02]
> Hello, I am preparing the new silx package and I got these error messages
> from adequate
>
> This package produce the silx python module but install also a bunch of files
> for qtdesigner
> in the rules file with this command.
>
> # install the qtd
[Andreas Tille, 2018-08-04]
> for the new version of python-pyvcf[1] I get
>
> W: python3-pyvcf: python-module-in-wrong-location
> usr/lib/python3.7/dist-packages/vcf/ usr/lib/python3/dist-packages/vcf/
> W: python3-pyvcf: python-module-in-wrong-location
> usr/lib/python3.7/dist-packages/vcf/par
[Sandro Tosi, 2018-08-03]
> https://packages.debian.org/unstable/pypi2deb
I uploaded new version today, `py2dsp --profile dpmt` now generates
salsa/gbp git repo instead of alioth/dpm
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[PICCA Frederic-Emmanuel, 2018-08-04]
> once debianize, is there a command which allow to update the control
> file for a new upsteam version in order to take into account the new
> python dependencies ?
>
> It would simplify a lot the maintenance of python packages.
>
> py2dsp update
remove con
> I've also kept the full upstream history in the upstream branch,
> assuming this to be more robust and powerful. For example, this allows
> to directly cherry-pick commits into the patch queue.
you can add remote repository and cherry-pick upstream commits as you
like
> Since both these practi
> rtupdate and postinst / prerm hooks for python3 packages currently call
> py3{compile,clean} which only operates on cpython3.
>
> 5. Something else?
modify these files and ship (renamed ones) in pypy3 package:
/usr/share/python3/runtime.d/public_modules.rtinstall
/usr/share/python3/runtime.d/pu
[Piotr Ożarowski, 2018-08-27]
> > rtupdate and postinst / prerm hooks for python3 packages currently call
> > py3{compile,clean} which only operates on cpython3.
> >
> > 5. Something else?
>
> modify these files and ship (renamed ones) in pypy3 package:
> err, you meant for python3-foo packages, so I guess option 3 is the best
> one.
err again (sorry, to many things at once), I meant option 4 (I can
change dh-python to generate additional checks for pypy{compile,clean})
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Matthias Klose, 2018-09-25]
> > how about generating dependencies on python2.7 and moving
> > pycompile/pyclean there as well (this also solves pre-dependency issue)
> >
> >> - Not having a python package in bullseye (buster+1), but a
> >>python2 package doesn't point to any "default" anymor
> > err again (sorry, to many things at once), I meant option 4 (I can
> > change dh-python to generate additional checks for pypy{compile,clean})
>
> That'd be pypy3{compile,clean}
this is now available in dh-python 3.20180927. Only postinst files are
checking for pypy3compile, though. py3clean i
[Ole Streicher, 2018-09-28]
> For one of my packages (sunpy), I want to complete the switch to pybuild
> by removing the custom (and quite unperfect) dh_override_auto_test rule.
>
> Currently, I have the following lines in d/rules:
>
> override_dh_auto_test:
> python -m pytest sunpy -k "not
Control: tags -1 -help
Control: tags -1 patch
> I tried to fix the issue reported below by using
> dh_python3 --no-ext-rename
> (see [1]) but this has no effect and the resulting package just
> contains
well, --no-ext-rename should not be used for public modules (I cannot
imagine a single case
[PICCA Frederic-Emmanuel, 2018-10-12]
> to my opinion, the code is modify in place with 2to3.
> So the code on the source after the configuration is already converted to
> python3.
> And during the build process, with python2 the code is copied as it in the
> .pybuild place for python2
> with py
[Ole Streicher, 2018-10-20]
> W: python3-astropy: python-module-in-wrong-location
> usr/lib/python3.7/dist-packages/astropy/
> usr/lib/python3/dist-packages/astropy/
> W: python3-astropy: python-module-in-wrong-location
> usr/lib/python3.7/dist-packages/astropy/coordinates/
> usr/lib/python3/di
> Since I polished python-lzma I uploaded the package anyway with new
> Vcs fiels and other polishing stuff.
please don't remove -dbg packages, -dbgsym packages are useless for us, AFAICT
(python{,3}-foo-dbg packages contain modules for Python debug
interpreter, something that -dbgsym packages do
[Wookey, 2018-11-22]
> No advice on best way to start a python packaging template?
# apt install pypi2deb
$ py2dsp djangorestframework-filters
source package will be available in ./result/ (change it with --root)
you can add '--profile dpmt' if you want to maintain it inside DPMT
--
GPG: 1D2F A8
[Scott Kitterman, 2018-11-29]
> dh-python already doesn't use upstream version requirements when
> automatically
> extracting dependencies, so you have to check those yourself regardless of
> how
> you do it. This design decision was based on generally poor experiences with
> the accuracy of
[Daniele Tricoli, 2018-12-29]
> I'm already a member of DPMT (in the salsa group with my
> eriol-guest account), but now I have a DD account (eriol) and I would
> like to start using it.
congrats! :)
> Please add my DD account to DPMT group on salsa: vvidic
done :)
901 - 1000 of 1020 matches
Mail list logo
