It looks like this commit enabled MPI support in the Debian builds:
https://salsa.debian.org/science-team/h5py/commit/e5251eed6a64b7ac259a92d8509b54e4335ab3d2
Thanks Lucas. I vaguely recall that I did actually package it, but never
managed to interest anyone in sponsoring it, and then got bored of
trying to do Debian packaging.
It looks like there is now a python3-sympy package in Debian, so I think
you can close this.
Package: gir1.2-packagekitglib-1.0
Version: 1.0.1-2
Severity: normal
According to the packagekit docs, the arch filter should only return packages
matching the system architecture:
http://www.freedesktop.org/software/PackageKit/gtk-doc/introduction-ideas-
filters.html
Using pkcon, this works:
$
Package: python-pexpect
Version: 2.4-1
Severity: normal
Tags: patch
There is a new upstream release (3.0), which includes Python 3 support. The
attached packaging works (as far as I can tell) with the new release. It builds
python3-pexpect and runs the test suite.
-- System Information:
Debian
On 21 June 2013 06:46, Anton Gladky gl...@debian.org wrote:
please, consider to maintain the package in Debian-Science team.
I would have no objections to that, but the Python 2 Sympy packages are
already maintained in Debian-Python, so I think it makes sense to keep them
in the same place.
Package: wnpp
X-Debbugs-Cc: debian-de...@lists.debian.org
Package: wnpp
Severity: wishlist
Owner: Thomas Kluyver tho...@kluyver.me.uk
* Package name: python3-sympy
Version : 0.7.2
Upstream Author : Aaron Meurer asmeu...@gmail.com
* URL : http://sympy.org/
* License
Forwarded upstream:
https://sourceforge.net/apps/mantisbt/modgnutls/view.php?id=16
Thanks, I've committed that to SVN.
Thanks for the bug report. I've fixed this upstream:
https://github.com/takluyver/pyxdg/commit/7a6e107db8d5be45c6b0d06d8092b6e7fec82449
I think I had over-eagerly implemented the latest version of the spec,
which says that .desktop files are UTF-8, without looking at the history of
it.
Best
On 28 September 2012 03:57, Arnaud Fontaine ar...@debian.org wrote:
This is just a cosmetic change, as it does not bring anything,
especially considering that 'set -e' is used to make sure that the build
process fails if one of the command fails.
I hope Barry will chime in here - I'm
I think Barry's key suggestion was to avoid using for loops to handle
multiple versions of Python 3. The example in LibraryStyleGuide uses
rules like this:
build-python%:
python$* setup.py build
override_dh_auto_build: $(PYTHON3:%=build-python%)
dh_auto_build
CCed Barry in case
I think this should be closed now - IPython has no dependencies on
Numeric, and there's no longer a specific scipy profile.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Is $XDG_MENU_PREFIX set? If it is set to gnome-, pyxdg should
correctly pick gnome-applications.menu as the default, as per the spec
[1].
What is the function of the debian-menu.menu file from menu-xdg? It
was added as a fallback (see bug #654978 [2]), but I'm not sure what
it stores.
[1]
I'm happy to add support for $XDG_RUNTIME_DIR, but I don't know what
the most common fallback directory is if the environment variable is
not set.
The spec is unhelpfully vague: If $XDG_RUNTIME_DIR is not set
applications should fall back to a replacement directory with similar
capabilities and
I'm just triaging bugs for PyXDG. It seems that getName() returns a
unicode string suitable for the current locale. I'd consider that the
expected behaviour. I believe modern GUI toolkits work with unicode
(I'm familiar with Qt, which certainly does).
Do you think that it should return an 8-bit
There's a new upstream release (0.20), which supports Python 3 and
includes several of the patches Debian has against 0.19.
http://freedesktop.org/wiki/Software/pyxdg
it's already been packaged in Ubuntu, so it should be simple to copy
that and adjust it.
--
To UNSUBSCRIBE, email to
Thanks, Jakub, I've committed that patch.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: python-tz
Version: 2011h-1
Severity: minor
From review when merging packaging changes into Ubuntu [1]. The debian/rules
file could be simplified following the recommendations for Python libraries
at [2].
Also, it looks like the current rules file doesn't run any tests, although it
Package: wnpp
Severity: wishlist
Owner: Thomas Kluyver tho...@kluyver.me.uk
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: python-notify2
Version : 0.1
Upstream Author : Thomas Kluyver tho...@kluyver.me.uk
* URL : http://pypi.python.org/pypi/notify2
Package: wnpp
Severity: wishlist
Owner: Thomas Kluyver tho...@kluyver.me.uk
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name : python-notify2
Version : 0.1
Upstream Author : Thomas Kluyver tho...@kluyver.me.uk
* URL : http://pypi.python.org/pypi/notify2
Python 3 support is only in the development version at present. It
should be released as 1.2.0.
I've got daily builds of matplotlib, including Python 3 builds, in a
PPA [1]. It seems to be working, although the most recent build failed
for reasons I haven't yet investigated. My changes to the
Package: wnpp
Severity: wishlist
Owner: Thomas Kluyver tho...@kluyver.me.uk
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: python3-dateutil
Version : 2.0
Upstream Author : Gustavo Niemeyer gust...@niemeyer.net
* URL : http://labix.org/python-dateutil
The attached patch against the debian/ folder gets a python3-numpy
(and -dbg) package built. It may well need some refinement, and I
haven't considered how best to handle dh_numpy and the ABI/API
versions, so those parts are only in the Python 2 python-numpy package
at present.
Thomas
Hi,
Thanks for the bug report. It's been fixed in trunk (which will become v
0.11). For more details, see the pull request here:
https://github.com/ipython/ipython/pull/251
Best wishes,
Thomas
24 matches
Mail list logo
