Re: qscintilla2: package Python 3 bindings
On 14 March 2012 04:13, Scott Kitterman wrote: > I did have to make some additional changes, such as using a policy > compliant > binary name in python3, as we did for PyQt4 (python3-pyqt4.qsci) and using > dh_sip3 for the python3 package. You can see the details in the DPMT SVN > if > you want. > I've been and looked, and it mostly makes sense to me. A couple of questions: Is the policy for binary package names simply to use python3- followed by the lowercased name that you'd import? You changed the packaging to build for all supported Python 3 versions, rather than only the default (although I think only 3.2 is currently supported, anyway). I'd originally had it like that, but when I looked at the PyQt4 packaging, it was only targeting the default version (py3versions -vd), so I followed suit for qscintilla. How do we decide which option to use? Thanks, Thomas
Re: qscintilla2: package Python 3 bindings
On Wednesday, March 14, 2012 12:41:32 PM Thomas Kluyver wrote: > On 14 March 2012 04:13, Scott Kitterman wrote: > > I did have to make some additional changes, such as using a policy > > compliant > > binary name in python3, as we did for PyQt4 (python3-pyqt4.qsci) and > > using dh_sip3 for the python3 package. You can see the details in the > > DPMT SVN if > > you want. > > I've been and looked, and it mostly makes sense to me. A couple of > questions: > > Is the policy for binary package names simply to use python3- followed by > the lowercased name that you'd import? Yes (or python-* for python packages). Sometimes due to case issues you've got no choice but to deviate: import DNS python-dns import dns python-dnspython For python-qt4 we decided it was not worth the trouble of a complex transition to rename it's binaries to be policy compliant. > You changed the packaging to build for all supported Python 3 versions, > rather than only the default (although I think only 3.2 is currently > supported, anyway). I'd originally had it like that, but when I looked at > the PyQt4 packaging, it was only targeting the default version (py3versions > -vd), so I followed suit for qscintilla. How do we decide which option to > use? python3.2 is the only supported python3 at the moment, so it doesn't affect things either way. PyQt4 should be building for all versions too, so I'll go back and check that. Scott K P. S. I'm subscribed to the list, so no need to cc me. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4916687.Jx4C0YJjbz@scott-latitude-e6320
Re: qscintilla2: package Python 3 bindings
On Mar 14, 2012, at 12:41 PM, Thomas Kluyver wrote: >You changed the packaging to build for all supported Python 3 versions, >rather than only the default (although I think only 3.2 is currently >supported, anyway). I'd originally had it like that, but when I looked at >the PyQt4 packaging, it was only targeting the default version (py3versions >-vd), so I followed suit for qscintilla. How do we decide which option to >use? It would be nice to build for all supported Python 3 versions. Python 3.3 is currently scheduled for August of this year, but I'm hoping we'll start seeing it show up in Debian around the time of the first beta in June. Go to pyvideo.org and look for Benjamin Peterson's talk on why Python 3.3 will be amazing. Also, there's Brian Curtin's summary from the language summit at Pycon 2012. http://blog.python.org/2012/03/2012-language-summit-report.html Also, take a look at recent python-dev email. Guido has been pronouncing on a slew of PEPs so expect to see a lot of great activity in the next few weeks. While he hasn't pronounced on a namespace packages PEP yet, we had some long discussion at the Pycon sprints about it, and I think there is a very high likelihood that this will (finally!) get solved in Python 3.3, and it will work out well for Debian packagers. There's also an incredible amount of activity around porting to Python 3, so keep an eye on upstreams as support start to land. Thanks so much for your own porting work! Cheers, -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120314084055.3bbc1b59@resist
Re: qscintilla2: package Python 3 bindings
On 14/03/12 15:40, Barry Warsaw wrote: > It would be nice to build for all supported Python 3 versions. Python 3.3 is > currently scheduled for August of this year, but I'm hoping we'll start seeing > it show up in Debian around the time of the first beta in June. That's too late for it to be relevant for Wheezy, tbh. I don't think a first beta should be in a Debian stable release, and the release team hopes to freeze in June (at which point advancing from beta to final is not a thing that should happen). S -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f60c120.1040...@debian.org
Re: qscintilla2: package Python 3 bindings
On 14 March 2012 16:02, Simon McVittie wrote: > That's too late for it to be relevant for Wheezy, tbh. I don't think a > first beta should be in a Debian stable release, and the release team > hopes to freeze in June (at which point advancing from beta to final is > not a thing that should happen). > I imagine it can get into Ubuntu's Q cycle, for release in October, though. Thomas
Re: qscintilla2: package Python 3 bindings
On Wednesday, March 14, 2012 04:02:40 PM Simon McVittie wrote: > On 14/03/12 15:40, Barry Warsaw wrote: > > It would be nice to build for all supported Python 3 versions. Python > > 3.3 is currently scheduled for August of this year, but I'm hoping > > we'll start seeing it show up in Debian around the time of the first > > beta in June. > > That's too late for it to be relevant for Wheezy, tbh. I don't think a > first beta should be in a Debian stable release, and the release team > hopes to freeze in June (at which point advancing from beta to final is > not a thing that should happen). It would be nice to have it in Experimental though. There are some bits of multi-version support for Python 3 that still need work and we could work on that with 3.3 and a new python3-defaults in experimental. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7882624.6Zvfr1ysqJ@scott-latitude-e6320
Re: qscintilla2: package Python 3 bindings
On Mar 14, 2012, at 01:27 PM, Scott Kitterman wrote: >It would be nice to have it in Experimental though. There are some bits of >multi-version support for Python 3 that still need work and we could work on >that with 3.3 and a new python3-defaults in experimental. +1 -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120314105141.67e5d185@resist
Bug#664019: ITP: lintian4python -- Debian package checker (for Python packages)
Package: wnpp Severity: wishlist Owner: Jakub Wilk * Package name: lintian4python Upstream Author : Jakub Wilk * URL : https://bitbucket.org/jwilk/lintian4python/ * License : GPL-2+ Programming Lang: Perl Description : Debian package checker (for Python packages) Lintian dissects Debian packages and reports bugs and policy violations. It contains automated checks for many aspects of Debian policy as well as some checks for common errors. This package provides an experimental flavor of lintian designed to check packages implemented in Python. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120314221305.ga6...@jwilk.net
