Re: Request to join PAPT (Was: Bug#914230: ITP: git-imerge -- incremental merge and rebase for git)
Dear Ondrej, > I don't see any merge requests for PAPT. Mea culpa; I misread this as DPMT as you have inferred. > I think it's better to do smaller changes/merge request. mwei, can you > split it to more smaller merge requests please? I would obviously heartily endorse this philosophy but I wonder that for expediency and to correct the now long-incorrect information I suggest we adjust our tolerance here. However, Mwei please do indeed split these into smaller MRs or commits. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Request to join PAPT (Was: Bug#914230: ITP: git-imerge -- incremental merge and rebase for git)
James Clarke wrote: > It turns out policy.rst is lying, I don't have permission to create a > repository. Therefore I would like to request to join PAPT, please (and > accept the policy even in spite of its lies). Python team, can we merge the pending Policy changes? It's getting a little frustrating reading these (or similar; not sure if this particular case is addressed…) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: request to join PAPT
Hi Stéphane, > I guess the policy should be updated to remove the references to Alioth > in 'joining the team' section: > 'he appears [...] on Alioth's project page. Debian developers: [...] > you'll get a "sponsor" role on Alioth.' Indeed, please go ahead and create an MR to do this… (… and someone please review and merge the outstanding ones!) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: want to join DPMT
Felix, > I have no experience with debian packages in a git repository. And I > wonder why your policy stats that git-dpm is favoured. In the > pyotherside salsa git there's a commit by Ondřej Nový that it has been > converted to gpb layout [2] The documentation is out of date; we use gbp. There is actually a parallel thread discussing this and it should be fixed soon; we have a number of MRs pending. Indeed, what is the status of this? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
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 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: [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 `-
Re: Team uploaded python-lzma - any hint how to deal with xz compressed files when using Python3
Andreas, > Since I can not really imagine that it should be hard to deal > natively with XZ compressed files when using Python3: Am I > missing something and there is a competing module? I am not sure what you are asking here, sorry. Something to do with the Debian packaging or whether there are other Python libraries for dealing with compressed files? If the latter, then debian-python is probably off-topic for such general Python questions, but diffoscope happens to be using libarchive. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
Picca, Hi PICCA Frederic-Emmanuel, > Hello, here a diff between the python3.6 and python3.7 modules Please use "unified" (ie. diff -u, possibly diff -urNad) over old-style diffs in future > < ord(sup): normal for (normal, sup) in TO_SUPERSCRIPT.items()} > > ord(sup): normal for (normal, sup) in iter(TO_SUPERSCRIPT.items())} No expert and I assume it works, but this doesn't "smell" right to me. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
Andreas, > Before I discuss this with upstream I'd like to share another observation: > There is some 2to3 magic applied to the source code which has the effect > that Assuming it's upstream's 2to3 magic, then I would speak to them. Alas, I am new to this package too — good luck and I hope I was of some initial help. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: TypeError: ord() expected a character, but string of length 3 found (Was: Updated python-uncertainties)
Andreas,
> > File "/usr/lib/python2.7/dist-packages/uncertainties/core.py", line 946,
> > in
> > ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
Please always provide a minimal testcase, otherwise people have to do a
lot of work simply to get where you are..
$ cat testcase.py
# coding=utf-8
TO_SUPERSCRIPT = {
0x2b: '⁺',
0x2d: '⁻',
0x30: '⁰',
0x31: '¹',
0x32: '²',
0x33: '³',
0x34: '⁴',
0x35: '⁵',
0x36: '⁶',
0x37: '⁷',
0x38: '⁸',
0x39: '⁹'
}
#! Python 2.7+ can use a dictionary comprehension instead:
FROM_SUPERSCRIPT = {
ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
$ python2 testcase.py
Traceback (most recent call last):
File "testcase.py", line 18, in
ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
File "testcase.py", line 18, in
ord(sup): normal for (normal, sup) in list(TO_SUPERSCRIPT.items())}
TypeError: ord() expected a character, but string of length 3 found
Under Python 2.x, list(TO_SUPERSCRIPT.items()) is:
[(43, '\xe2\x81\xba'),
(45, '\xe2\x81\xbb'),
(48, '\xe2\x81\xb0'),
[…]
]
ie. strings with a length of 3 whilst ord() takes a single char. These
should therefore be probably defined as:
TO_SUPERSCRIPT = {
0x2b: u'⁺',
0x2d: u'⁻',
[…]
.. instead, but I haven't tested or confirmed or anythinged that; I'll
leave it with you and upstream.
I also couldn't help notice:
Vcs-Browser: https://salsa.debian.org/debian/python-uncertainties
Vcs-Git: https://salsa.debian.org/debian/python-uncertainties.git
.. yet:
Maintainer: Debian Python Modules Team
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Re: python-hl7 is maintained in med-team Git - please remove copy in DPMT
Hi Andreas, > Kind regards and thanks for trying to enhance the packaging anyway > despite the effort was a bit of (hopefully automated) wasted time Totally automated changes on my part. Go ahead an make your best judgement on the future of this package. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Fwd: next version of csvkit
Ghislain Vaillant wrote: > > On the current subject, I also agree we should not drop prematurely > > packages targeted to Python 2. The Lintian tag in question does not suggest maintainers should be removing existing Python 2 support from packages. It merely suggests that you should think twice before *adding* Python 2 support when putting together a new package. Such support can always be added later after user demand. The idea is that if we never add such support we've not only saved ourselves some effort in the future, we've also encouraged the general adoption of Python 3. Perhaps this is not clear in the tag/warning/description? This appears to be a constant source of confusion/frustration, alas. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: [Python-modules-team] python-django_1.10~beta1-1_amd64.changes ACCEPTED into unstable
It was an error; I intended to upload to experimental. Wil fix in the morning.. My apologies for the noise. On Sun, 26 Jun 2016, at 03:38 AM, Brian May wrote: > Not sure if uploading this to unstable so soon was a good idea... There > are going to be packages that break as a result, and possibly not fair > to expect them to support Django 1.10 before if it even released. > > Debian FTP Masters <ftpmas...@ftp-master.debian.org> writes: > > > Accepted: > > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > Format: 1.8 > > Date: Sat, 25 Jun 2016 19:17:49 +0200 > > Source: python-django > > Binary: python-django python3-django python-django-common python-django-doc > > Architecture: source > > Version: 1.10~beta1-1 > > Distribution: unstable > > Urgency: medium > > Maintainer: Debian Python Modules Team > > <python-modules-t...@lists.alioth.debian.org> > > Changed-By: Chris Lamb <la...@debian.org> > > Description: > > python-django - High-level Python web development framework (Python 2 > > version) > > python-django-common - High-level Python web development framework (common) > > python-django-doc - High-level Python web development framework > > (documentation) > > python3-django - High-level Python web development framework (Python 3 > > version) > > Closes: 801744 > > Changes: > > python-django (1.10~beta1-1) unstable; urgency=medium > > . > >[ Chris Lamb ] > >* New upstream beta release. > >* Drop fix-25761-add-traceback-attribute.patch; applied upstream. > > . > >[ Raphaël Hertzog ] > >* Remove obsolete /etc/bash_completion.d/django_bash_completion on > > upgrade. > > Closes: #801744 > > Checksums-Sha1: > > ac5f8e690dce89b5bc915bba3d5b1a3eea4655b0 2788 > > python-django_1.10~beta1-1.dsc > > d2e39b1a37955f737935bf0af7ec2a3ddba1ff78 7600640 > > python-django_1.10~beta1.orig.tar.gz > > 15dd133b50ddf6edc02fc6802199c726d28322ae 24512 > > python-django_1.10~beta1-1.debian.tar.xz > > Checksums-Sha256: > > 9af1a6946bc506cfdc582967a34fae4de14aa1f5147102261673856d69ada407 2788 > > python-django_1.10~beta1-1.dsc > > d8ef9aef259d68a452d5ae1a6f60793e8c10c609dbbe9e7412d47ac21e6d4245 7600640 > > python-django_1.10~beta1.orig.tar.gz > > 30080bb965def54da24d90963a69361311b8c095dc0dff0b59ae7135c8937f30 24512 > > python-django_1.10~beta1-1.debian.tar.xz > > Files: > > 77c5582745a10cee41df0be3675d8a3a 2788 python optional > > python-django_1.10~beta1-1.dsc > > c2f10b2d1453adc68e37132c3304317a 7600640 python optional > > python-django_1.10~beta1.orig.tar.gz > > 84ad1186875dec6008e7b218a3f23dad 24512 python optional > > python-django_1.10~beta1-1.debian.tar.xz > > > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v1 > > > > iQIcBAEBCAAGBQJXbsEOAAoJEB6VPifUMR5YKNQQAIuNS9fC2FHA4jKTc+2c4vxU > > YatQABaW5cvFZKlaEoOAUWZSktluruTNIPZ5jht30ap2bzPWG6n8AMoYciq5AlU3 > > HwHXMi/554SYXO/CKhVjvrmwGEdYlQdXZhG7NPzZ2ysC/6sWLM1q/503uWG5M9lG > > JykjN1H3iCZVPW8Fy36TmoFPJOOfrrvicFPzqk12BbspYOMxQrhaGowN+HcETaTu > > 2U6kSPIfs7o3dgUep3BKDA+xVLe3WeWZc+yj0S3ptNh4PWW31V1tfp8v0KRD9wJR > > /YUtVS2wfS1p9PReoBy58af3uWr3Yl2cHCCTFLz5SymyX/arxCOVEGm6LE2YTRHI > > qghkBdT/mUvEHUpQahDWKNiE+hIRWH94V2bcqNYltt508tN0CKRSF+8YtQo8qwev > > NTFdXrdY+qa3DIpsKMQNMu6oMLYH5q97FijuzahisPaTJZvAoDaUtMTBHI6KGASd > > Q9drr52ijUTXEgCE7n5dAHIOJGZNv1HJ0L7FmHo0RZVnP4TAfpNpUmrp82zL3yhK > > +GA6U4HoKl4cXZsSh3Fct8O817/A6rNh9sk8noUKQvIILcwfq1xnCPiDsAOIENsP > > 9/qxZ535tSYmNgC0eyECYGcssLzFnbaqcDDGPioNFvySOtlQ/IB+plw7fHI5rllp > > qXu1/eIGf5duehwIXnu8 > > =t5A5 > > -END PGP SIGNATURE- > > > > > > Thank you for your contribution to Debian. > > > > ___ > > Python-modules-team mailing list > > python-modules-t...@lists.alioth.debian.org > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team > -- > Brian May <br...@linuxpenguins.xyz> > https://linuxpenguins.xyz/brian/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Package names for docutils writers
Michael Schutte wrote: I’ve considered this, of course, but I don’t know if this is really the right thing to do given the frontend’s size (3 kiB in my case). [..] I’m not sure whether this is desirable. Heh, no. Anyway, I'd be more than happy to rename to fit a consensus/scheme. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Re: Package names for docutils writers
Michael Schutte wrote: So I think the following naming style is appropriate: docutils-reader-foo [..] These are components of the Docutils system; and such extensions can be of several distinct purposes (hence “reader”, “transform”, “writer”, etc.) [..] At the moment it’s really just us three. So, Chris, what do you think? :-) Ah, I like this. We all agreed? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Re: Package names for docutils writers
Michael Schutte wrote:
And then there is rst2pdf (Chris Lamb) which does the all-in-one thing
in a single eponymous .deb.
[..]
Since I care about consistency, I’d like to get this sorted out. My
personal preference would be “python-docutils-X”: it’s short,
reasonably precise and explanatory.
Hm, I do like your proposed naming scheme, but the current package name
seems to be more explanatory than python-docutils-pdf, and the foo2bar
naming scheme has some history in the PostScript world. I guess this all
depends on your level of abstraction.
I wonder whether having two packages would be overkill? eg.
Package: python-docutils-pdf
Depends: python-reportlab, [..]
Contains the library.
Package: rst2pdf
Depends: python-docutils-pdf (= ${binary:Version}, [..]
Contains /usr/bin/rst2pdf, manpage, etc.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
signature.asc
Description: PGP signature
