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
* 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
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
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
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
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
6 matches
Mail list logo
