Allow installation on buster of a package not supporting 3.7 (async/await syntax error when generating bytecode)
Hello list, I have a package working perfectly fine on Pyrhon 3.6 but using async/await methods so it cannot work on python 3.7 at the moment. During package compilation, I popd 3.7 from supported version returned by py3version and it allows me to build the package just fine: Problem: I cannot install it. Despite 3.7 was not "enabled" during build, when installing debian helpers try to compile bytecode for both 3.6 and 3.7 and fails. Is there any way to workaround that ? Thanks in advance, Adam. PS: I'm aware this is transitional and the package MUST support 3.7, but I kinda need a fast workaround, like right now.
pytest 3.9.3 in experimental
Hi, I uploaded pytest version 3.9.3 into experimental. Please test it with your packages and report me any issues. If there will be no issues I will upload it into unstable after ~2 weeks from now. Thanks. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: DPMT: join request
Hi, st 31. 10. 2018 v 14:51 odesílatel Stewart Ferguson napsal: > I'd like to join the DPMT team. > welcome. :) -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: [salsa] please add me as member of DMPT
Hi, st 7. 11. 2018 v 6:54 odesílatel Samuel Henrique napsal: > Sorry, I switched groups, I need access to the PAPT group, I'm already > part of the DPMT one. > added. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: [Salsa] DPMT Join Request from @mwei
Hi, so 3. 11. 2018 v 1:37 odesílatel Yao Wei napsal: > As stated in the bug #912656 (which the first email is also CC'd to this > mailing list), I would like to join the DPMT team, for uploading > python-fs package for py2 and py3. > did you read our policy ( https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst) and do you accept it? Thanks. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: [Salsa] DPMT Join Request from @mwei
Hi, I read the policy, but I found several questions about it. 1. We are now using Salsa but the policy remains in Alioth. 2. We are probably not preferring using git-dpm but gbp + quilt right now. (not sure about this though: I was doing git-dpm in a Python package maintained outside Python teams but another DD told me that I should use gbp + quilt) Other than these two I have no problem about the rest of the policy. Yao Wei (This email is sent from a phone; sorry for HTML email if it happens.) > On Nov 8, 2018, at 18:45, Ondrej Novy wrote: > did you read our policy > (https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst) > and do you accept it?
Re: pytest 3.9.3 in experimental
Roger That El jue., 8 de nov. de 2018 a la(s) 06:09, Ondrej Novy (n...@ondrej.org) escribió: > Hi, > > I uploaded pytest version 3.9.3 into experimental. Please test it with > your packages and report me any issues. If there will be no issues I will > upload it into unstable after ~2 weeks from now. > > Thanks. > > -- > Best regards > Ondřej Nový > > Email: n...@ondrej.org > PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B > > -- Arias Emmanuel http://eamanu.com Github/Gitlab; @eamanu Debian: @eamanu-guest
Re: [Salsa] DPMT Join Request from @mwei
Hi Yao Wei, > 1. We are now using Salsa but the policy remains in Alioth. > > 2. We are probably not preferring using git-dpm but gbp + quilt right > now. (not sure about this though: I was doing git-dpm in a Python > package maintained outside Python teams but another DD told me that I > should use gbp + quilt) You are very welcome on the team. Once formally accepted, your first job is seemingly to update the linked document to reflect the above - thanks! Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Updating the Python Modules *Team* policy
[
I'm *not* talking about the Python "packaging" Policy[0], which is under the
prerogative of the python{,3}-defaults maintainers.
[0] https://www.debian.org/doc/packaging-manuals/python-policy/
]
Dear all,
The DPMT policy[1] is still talking about Alioth and git-dpm, which is ever so
slightly outdated. valhalla submitted a MR[2] a while ago to fix some of these
references, but that ended up being a dead letter.
[1]
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
[2] https://salsa.debian.org/python-team/tools/python-modules/merge_requests/1
There was some confusion about who is the caretaker of this policy, I think
stemming from the fact that the "main" Python packaging policy also needs some
updates.
I feel the consensus is that that PR should just get merged and that the DPMT
policy can just be updated by team consensus on this list. Consider this a
heads up that I'll merge this in the next few days, unless there's any issue
people can come up with.
A MR describing the git-buildpackage workflow would also be appreciated.
Cheers,
--
Nicolas Dandrimont
BOFH excuse #378:
Operators killed by year 2000 bug bite.
signature.asc
Description: PGP signature
Re: Allow installation on buster of a package not supporting 3.7 (async/await syntax error when generating bytecode)
Hi! * Adam Cécile [2018-11-08 09:15:59 +0100]: > Hello list, > > > I have a package working perfectly fine on Pyrhon 3.6 but using async/await > methods so it cannot work on python 3.7 at the moment. > During package compilation, I popd 3.7 from supported version returned by > py3version and it allows me to build the package just fine: > > Problem: I cannot install it. Despite 3.7 was not "enabled" during build, > when installing debian helpers try to compile bytecode for both 3.6 and 3.7 > and fails. Is there any way to workaround that ? You can use the bcep (bytecompile exception pattern) mechanism. The documentation can be found in dh_python3(1)[1] and /usr/share/doc/dh-python/README.PyDist, and you can find some examples in codesearch. [1] https://manpages.debian.org/unstable/dh-python/dh_python3.1.en.html#bcep_files HTH, -- Nicolas Dandrimont BOFH excuse #227: Fatal error right in front of screen signature.asc Description: PGP signature
Re: Updating the Python Modules *Team* policy
Hi Nicolas, > I feel the consensus is that that PR should just get merged and that the DPMT > policy can just be updated by team consensus on this list. Consider this a > heads up that I'll merge this in the next few days, unless there's any issue > people can come up with. Great idea. Indeed, lets just get this merged (why wait?) so we don't confuse or even scare away potential contributors with outdated docs. We can always continue to iterate on it or even revert parts of it, after all. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Updating the Python Modules *Team* policy
Hi, I am proposing another merge request: https://salsa.debian.org/python-team/tools/python-modules/merge_requests/2 Prominent changes are follows: * Change git repo from Alioth to Salsa * Suggests to use git-buildpackage and quilt format instead of git-dpm - Some unrelevant paragraphs on git-dpm are also removed * Changes strong discourgement of deviating from the policy since we are doing so recently. On Thu, Nov 08, 2018 at 08:42:13AM -0500, Chris Lamb wrote: > > I feel the consensus is that that PR should just get merged and that the > > DPMT > > policy can just be updated by team consensus on this list. Consider this a > > heads up that I'll merge this in the next few days, unless there's any issue > > people can come up with. > > Great idea. > > Indeed, lets just get this merged (why wait?) so we don't confuse > or even scare away potential contributors with outdated docs. We > can always continue to iterate on it or even revert parts of it, > after all. Thanks, Yao Wei signature.asc Description: PGP signature
Re: Updating the Python Modules *Team* policy
Yao Wei, > I am proposing another merge request: > > https://salsa.debian.org/python-team/tools/python-modules/merge_requests/2 Another in the sense of "replacing" or "in addition to" the one Nicolas already proposed we merge? (If the former, how is it superior?) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Updating the Python Modules *Team* policy
Hi, My merge request already incorporates what Nicolas proposed, So, I think that would mean both "replacing" and "in addition to" since my changeset is a superset to the previous one. The other changes are listed in my previous email. On Thu, Nov 08, 2018 at 10:45:15AM -0500, Chris Lamb wrote: > > I am proposing another merge request: > > > > https://salsa.debian.org/python-team/tools/python-modules/merge_requests/2 > > Another in the sense of "replacing" or "in addition to" the one > Nicolas already proposed we merge? > > (If the former, how is it superior?) Yao Wei signature.asc Description: PGP signature
