Re: Numpy dh_python2
On 16.03.2012 02:15, Thomas Kluyver wrote: After some trial and error, I've got it building python3-numpy (leaving python-support in place for Python 2) - a patch is attached. I've checked that I can install and import the built package. Changes and suggestions are welcome, and I expect there are better ways to do bits of it. I'm away for the weekend, so it'll be a few days before I can work on it again. For now, I've ignored the dh_numpy and ABI/API versions, but I guess we'll want to make Py3 versions of them. thanks for the patch. I'll upload it next week, re-adding myself as an uploader, apparently silently removed. Matthias -- 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/4f6333db.6080...@debian.org
Re: Numpy dh_python2
* Matthias Klose d...@debian.org, 2012-03-16, 13:36: re-adding myself as an uploader, apparently silently removed. Well, from my IRC log (2011-08-27): 22:43 jwilk morph_: Out of interest, did you ask the former Numpy co-maintainers if they are ok with removing them from Uploaders? : 22:43 morph_ jwilk: of course 22:43 jwilk Did they reply? 22:43 morph_ jwilk: no all of them, I gave 2 weeks of time to do that (Presumably no all is a typo for none.) Also, you surely received this mail, which is quite explicit: http://lists.debian.org/debian-devel-changes/2011/09/msg01361.html -- 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/20120316132921.ga7...@jwilk.net
Re: Numpy dh_python2
On 16 March 2012 13:35, Sandro Tosi mo...@debian.org wrote: Thanks a lot for your work! I just gave it a quick look (i.e. reading the patch) and it seems that would work (at least for the packaging part). It would be also nice if you could post your patch at 601...@bugs.debian.org, so also the BTS will be notified of the available patch. Great, thanks Sandro, I'll post it to the bug. Let me know if there's anything else I should be doing with it. Best wishes, Thomas -- 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/caovn4qgpt7vg32n0po1sag39li9qgl3td+kmgors8pya_yd...@mail.gmail.com
Re: Numpy dh_python2
Hi Thomas, On Fri, Mar 16, 2012 at 02:15, Thomas Kluyver tho...@kluyver.me.uk wrote: After some trial and error, I've got it building python3-numpy (leaving python-support in place for Python 2) - a patch is attached. I've checked that I can install and import the built package. Changes and suggestions are welcome, and I expect there are better ways to do bits of it. I'm away for the weekend, so it'll be a few days before I can work on it again. For now, I've ignored the dh_numpy and ABI/API versions, but I guess we'll want to make Py3 versions of them. Thanks a lot for your work! I just gave it a quick look (i.e. reading the patch) and it seems that would work (at least for the packaging part). It would be also nice if you could post your patch at 601...@bugs.debian.org, so also the BTS will be notified of the available patch. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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/CAB4XWXyPKa_7MKa_rX368N=dDdMfynSFWaXfneM2=1n7j78...@mail.gmail.com
Removing legacy XS-Python-Version support from python3-defaults
When Squeeze was nearing freeze, the definition of some aspects of python3 support were still new. There were some packages that used XS-Python-Version in debian control, instead of X-Python3-Version. There are now none (one package still has it in debian/control, but it's not actually used in the build system), so in the next python3-defaults upload, I plan to remove support for this from dh_python3 and py3versions. Scott K signature.asc Description: This is a digitally signed message part.
RFC: Adding discussion about required versions to Python policy
I've worked on a couple of dh_python3 bugs in the last few days and as a result, gotten my hands dirty on the Python 3 dependency generation code. This caused me to consider the question of specifying which Python 3 versions are supported by a package a little more closely. I have generally considered that if all Python (Python 3) versions supported in the development release were supported by the package, then there's no need to explicitly define the supported versions in the packaging (e.g. using X-Python-Version). Reality is, of course, slightly more complex. For Python 3, architecture independent packages that have no version specific code in them will always depend on python3 = 3.1.3-13~. So for these packages the minimum version requirement specified in X-Python3-Version isn't 3.2 (the current version in Wheezy), it's 3.1. Packages that will only work with Python 3 3.2 need this specifed in X-Python3-Version. I took a stab at adding some words to the Python policy to explain this. Comments please (diff attached). Scott K--- python-policy.txt 2012-03-16 23:29:14.384401914 -0400 +++ python-policy.new.txt 2012-03-16 23:46:06.460372010 -0400 @@ -398,16 +398,29 @@ Python 3) supported by the source package. Similarly, `X-Python3-Version' is used to specify the versions of Python 3 supported by the package. When not specified, they default to all - currently supported Python (or Python 3) versions. They are used by - some packaging scripts to automatically generate appropriate Depends - and Provides lines. The format of the field may be one of the - following: + currently supported Python (or Python 3) versions. + + They are used by some packaging scripts to automatically generate + appropriate Depends and Provides lines. The format of the field may + be one of the following: XS-Python-Version: = X.Y XS-Python-Version: = A.B, X.Y XS-Python-Version: A.B, X.Y XS-Python-Version: all + If the package supports all versions of Python/Python3 either + supported in or planned for the development release, as well as the + stable release, then `X-Python-Version' or `X-Python3-Version' may + generally be omitted from `debian/control'. The most common exception + to this is architecture independent Python 3 modules with no version + specific code. Since, unlike in Python, version specific directories + are not needed for Python 3, there is no need to constrain their + minimum Python 3 version to the supported versions. For these + packages, `X-Python3-Version' can only be omitted if the package + supports python3 = 3.1.3-13 and later (python3 3.0 was never a + supported Python 3 version in Debian). + The keyword all means that the package supports any Python version available but might be deprecated in the future since using version numbers is clearer than all and encodes more information. The @@ -416,6 +429,7 @@ 2.5, 2.6) work for `XS-Python-Version' and will continue to be supported, but are not recommended and will not be supported by `X-Python-Version' or `X-Python3-Version' after the Squeeze release. + The keyword current has been deprecated and used to mean that the package would only have to support a single version (even across default version changes). It must be ignored for Python 3 versions. signature.asc Description: This is a digitally signed message part.
