Package: python-cffi
Version: 1.11.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
testing/cffi0/test_verify.py ..s [ 35%]
[ 39%]
..
Package: wnpp
Severity: wishlist
Owner: Yaroslav Halchenko
* Package name: python-sounddevice
Version : 0.3.10
Upstream Author : Matthias Geier
* URL : http://python-sounddevice.readthedocs.io/
* License : MIT/X
Programming Lang: Python
Description
On Sat, 24 Feb 2018, Rock Storm wrote:
> What's the status of this issue?
it is stable. contributions would be welcome(d)
> Will it ever be a python3 binary package?
yes
> I fail to use the package 'python-pyglet' for a python3 application, I
> keep getting the following error even though th
Indeed, new releases are out and since 3.3.0 there is a new fixture
(caplog) which an increasing number of projects start to use, so
we would need an updated py.test to be able to package them (we run
tests at build time)
Cheers and thanks in advance
--
Yaroslav O. Halchenko
Center for Open Neur
oh -- since package is now under DPMT, I guess I will just take care
about updating it
Cheers,
On Fri, 14 Jul 2017, Yaroslav Halchenko wrote:
> Source: python-whoosh
> Version: 2.7.0-2
> Severity: normal
> Thanks for packaging/maintaining whoosh!
> We decided to use it for the
On Tue, 11 Jul 2017, Yaroslav Halchenko wrote:
> Package: python-virtualenv
> Version: 15.1.0+ds-1
> Severity: normal
> Not 100% sure if it is not a python-dbg or gdb issue, but I think it might as
> well be virtualenv:
> $> virtualenv --python=/usr/bin/python-dbg venv-dbg
Package: python-virtualenv
Version: 15.1.0+ds-1
Severity: normal
Not 100% sure if it is not a python-dbg or gdb issue, but I think it might as
well be virtualenv:
$> virtualenv --python=/usr/bin/python-dbg venv-dbg
Running virtualenv with interpreter /usr/bin/python-dbg
New python executable in /
Package: python-future
Version: 0.15.2-4
Severity: wishlist
Would be great and appreciated
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100,
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Archi
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python-git depends on:
ii git [git-core] 1:2.11.0-2
ii git-core1:2.11.0-2
ii python-gitdb2.0.0-2
pn python:any
python-git recommends no packages.
Versions of packages python-git s
Package: wnpp
Severity: wishlist
* Package name: airspeed-velocity
Version : 0.2
Upstream Author : ASV Authors
* URL : http://asv.readthedocs.io/,
https://github.com/spacetelescope/asv
* License : BSD-3
Programming Lang: Python
Description : Python benc
Source: python-aiohttp
Version: 1.1.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
While preparing for upload of fresh cython (0.25.2~b0-1) and running build of
rdepends python-aiohttp failed to build with
dh_auto_clean
I: pybuild base:184: py
On Wed, 16 Nov 2016, Sandro Tosi wrote:
> On Wed, Nov 16, 2016 at 6:23 PM, Yaroslav Halchenko
> wrote:
> > Unfortunately it seems
> > that python notebook support for jupyter is simply not present?! (thus
> > marked
> > at normal severity)
> i'
Package: jupyter-core
Version: 4.2.0-2
Severity: normal
It might be that it is just the RTFM and that I was stuck using good old
ipython-notebook for too long... but now that it is gone, I was expecting
jupyter package(s) to provide a replacement/transition. Unfortunately it seems
that python no
Package: python-pyld
Version: 0.6.8-1
Severity: minor
$> debcheckout python-pyld
declared git repository at
git://anonscm.debian.org/python-modules/packages/python-pyld.git
git clone git://anonscm.debian.org/python-modules/packages/python-pyld.git
python-pyld ...
Cloning into 'python-pyld'...
r
Package: python-scipy
Version: 0.17.0-1
Severity: important
pymvpa2 package FTBFS on mips atm
https://buildd.debian.org/status/fetch.php?pkg=pymvpa2&arch=mips&ver=2.4.3-1&stamp=1458051582
due to
Program received signal SIGILL, Illegal instruction
which if ran under gdb provides following detail:
Source: python-aiohttp
Version: 0.20.2-1
Severity: important
I have uploaded fresh cython few days back 0.23.4+git4-g7eed8d8-1 and while
testing reverse dependencies, saw that this package would now FTBFS due
to
...
'build/scripts-3.4' does not exist -- can't clean it
I: pybuild base:184: python3
Package: python-keyring
Version: 5.7.1-1
Severity: wishlist
Just heads up that there is a new upstream, BUT to provide smooth upgrade new
package would need to come to live to incorporate those backends which were
moved away into https://github.com/jaraco/keyrings.alt /
https://pypi.python.org/p
Package: python-smmap
Version: 0.8.3-1
Severity: normal
fresh release/snapshot of python-git needs updated/fixed version, so it would
be nice to see 0.8.3 in unstable to progress forward.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (900, 'testing'), (600
On Tue, 11 Aug 2015, Yaroslav Halchenko wrote:
> I will do it later today. Gitdb would need a kick then as well I guess
gitdb uploaded to unstable
python-git -- would like to get a closure on
https://github.com/gitpython-developers/GitPython/issues/336
most probably will upload the curr
I will do it later today. Gitdb would need a kick then as well I guess
On August 11, 2015 4:45:46 AM EDT, Hans-Christoph Steiner
wrote:
>
>Hey all,
>
>I just checked GitPython (aka python-git) and there are newer upstream
>releases available, so I wanted to check in on the status of updating
>it
> I have uploaded 0.11.0 in Sid.
Great! Thanks! I will hold my breath until it appears in the archive ;)
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist,Psychological and Brain Sciences Dept.
Dartmouth College
On Thu, 30 Jul 2015, Michael Fladischer wrote:
> Hi Thomas,
> it seems that there is one missing depeendency for python-mock-1.3.0
> still in experiamental: pbr-1.3.0
> Could you do an upload into unstable?
as far as I have checked, situation is more tricky -- circular
versioned depends: for
On Tue, 30 Jun 2015, Sandro Tosi wrote:
> Hello,
> I will need kinda urgently (few days) to backport
> python-tornado/4.2.0-1 to jessie, I can do it myself no problem, but
> wanted to check with you if you prefer to handle it yourself or if
> there's any problem if I do it.
If you do -- I would
upstream doesn't ship tests/ nor for w3lib, neither for scrapy. Dialog
began:
https://github.com/scrapy/w3lib/pull/34
scrapy needs testfixtures module, not in Debian, for quite a few tests
(and jmespath which is in debian)
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pym
Package: python-scrapy
Version: 0.24.2-1
Severity: wishlist
Just to let you know.
There was quite a bit of API changes http://doc.scrapy.org/en/1.0/news.html but
I don't see any reverse-dependencies on scrapy, so should be not that painful
whenever new version hits archive.
-- System Information
Package: python-pyglet
Version: 1.1.4.dfsg-2
Severity: normal
Due to the age of 1.1.4 (from 2010) I am marking this as normal. 1.2 was
released this Feb and we should upgrade unstable to it soonish!
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (900, 'testing'),
Package: python-tornado
Version: 3.2.2-1.1
Followup-For: Bug #779035
Fresh version of ipython 3.0 will require tornado >= 4.0 so fresh version would
be well appreciated! thanks!
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (30
Package: python-testtools
Version: 0.9.39-1
Severity: wishlist
I just saw that some matchers definitions are not exposed (absent in __all__),
so went upstream to see that was already fixed and that there is 1.5.0 release
in Nov 2014. So it would be really neat to get fresh testtools into
Debian pr
I was about to upload 0.3.2.1 into experimental but then decided to
enable testing and found that some tests point to regressions etc, so
decided to postpone. I will push though to svn the changes I have done
so far
see https://github.com/gitpython-developers/GitPython/issues/216
cheers
--
Yar
Package: python-git
Version: 0.3.2~RC1-3
Severity: wishlist
Please update the package, or let me know if I should do as a team
upload.
Cheers!
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental')
Architec
Package: python-git
Version: 0.3.2~RC1-3
Followup-For: Bug #739898
I am thinking about updating this package to current state of Git master
from upstream. I have asked about possible RC2 but haven't got response
so far:
https://github.com/gitpython-developers/GitPython/issues/164
I would also ap
Package: python-scrapy
Version: 0.24.2-1
Severity: wishlist
it should help to guarantee correct operation using system-wide
available versions of dependencees. Also it would help to install all
necessary packages (from Debian) for testing of scrapy (via apt-get
build-dep).
Thanks in advance!
--
Package: python-w3lib
Version: 1.5-1
Severity: wishlist
thanks in advance for updating the package!
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures:
Dear Julian, Sandro and the rest of the team.
Only with a slight tune up to the current state of the matplotlib in team's SVN
repository I have just uploaded to 2-days delayed, and then dcommitted to
svn including the tag.
Sandro, please let me know if I could reupload straight without any
delay.
On Sat, 05 Jul 2014, Vincent Bernat wrote:
> ❦ 4 mai 2014 09:15 +0200, Vincent Bernat :
> >> There is another problem on sparc that makes the build fail but it
> >> succeeds on s390x. I still have to figure out the remaining bug on
> >> sparc but it seems quite complex (and related to libffi)
On Wed, 29 Jan 2014, Vincent Bernat wrote:
> > python-cffi unit tests are failing on sparc and s390x arch. You can
> > find a patch to fix some of the problems here:
> >
> > https://bitbucket.org/cffi/cffi/commits/f3dabd52fbeb54e814e14120cb27ceae3ad266ce
> > There is another problem on sparc th
Package: python-pip
Version: 1.4.1-2
Severity: minor
$> pip --help | grep wheel
wheel Build wheels from your requirements.
$> pip wheel
ERROR: 'pip wheel' requires bdist_wheel from the 'wheel' distribution.
$> acsearch pip wheel
libpoe-component-dbiagent-perl - POE Compon
Package: python-numpy
Version: 1:1.7.1-3
Severity: wishlist
Just wanted to see if on s390x it is a known issue leading to
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724047 but can only know that
KNOWNFAIL=6, SKIP=5 on
https://buildd.debian.org/status/fetch.php?pkg=python-numpy&arch=s390x&v
Package: python-matplotlib
Version: 1.3.0-1
Followup-For: Bug #719384
yes -- this is a very inconvenient bug since prevents clean and build
operations on setup.py while $HOME is pointing to non-existing directory. As a
workaround I am doomed now to mkdir -p $$HOME (which is $(CURDIR)/build) in th
Package: python3-numpy
Version: 1:1.7.1-2
Severity: minor
$> python3 -c 'import numpy; print(numpy.__version__)'
1.8.0.dev-Unknown
$> python -c 'import numpy; print(numpy.__version__)'
1.7.1
just confused me and others for a bit:
https://github.com/pydata/pandas/issues/4263#issuecomment-210679
Package: python-bs4
Version: 4.2.0-2
Severity: normal
was checking upcoming pandas release and ran into various tests failures...
e.g. https://github.com/pydata/pandas/issues/4214
seems to be resolved if I upgrade (via seamless uupdate) to 4.2.1 which has
following changelog
= 4.2.1 (20130531) =
> Hello Julien and Yaroslav,
> thanks for remindig this: I was wondering about backporting requests but as
> noted by Yaroslav we have to investigate how many packages will break.
> On Wednesday 05 June 2013 08:30:55 Yaroslav Halchenko wrote:
> > It would be nice to know if
FWIW IIRC requests 1.x is not (fully) backward compatible with 0.12.x we
have in wheezy.
It would be nice to know if it would break any of the reverse
dependencies if backport gets uploaded (may be add NEWS entry to make it
obvious happen someone pull it from backports)
$> apt-cache rdepends pyth
"to mu or not to mu"
FWIW: for mpi4py I decided to avoid hardcoding the suffix:
diff --git a/debian/rules b/debian/rules
index 0688ac2..54e761d 100755
--- a/debian/rules
+++ b/debian/rules
@@ -54,10 +54,14 @@ override_dh_install:
done
: # Python 3
+ : # Can have python$$v symlin
oke_via-m.patch
parallelpython-1.6.2/debian/patches/30_ppworker_invoke_via-m.patch
--- parallelpython-1.6.2/debian/patches/30_ppworker_invoke_via-m.patch
1969-12-31 19:00:00.0 -0500
+++ parallelpython-1.6.2/debian/patches/30_ppworker_invoke_via-m.patch
2013-01-22 13:29:31.0 -050
+parallelpython (1.6.2-2) unstable; urgency=low
+
+ * Team upload
+ * Invoke ppworker via "python -m" avoiding addition of /usr/share/pyshared
+to sys.path (Closes: #620551)
+
+ -- Yaroslav Halchenko Tue, 22 Jan 2013 13:29:34 -0500
+
parallelpython (1.6.2-1) unstable; urgency=l
On Tue, 22 Jan 2013, Jakub Wilk wrote:
> * Yaroslav Halchenko , 2013-01-22, 12:28:
> >>One simple solution would be to run the script under the symlink
> >>path /usr/lib/pymodules/python2.6/ppworker.py.
> >>Then /usr/lib/pymodules/python2.6/ would be added (ag
Package: python-pp
Version: 1.6.2-2
Severity: wishlist
subj... changelog:
pp-1.6.3.
1) Added -P pid_file command line argument to ppserver.py
2) Modified print_stats() to output the number of active tasks.
3) Added SIGUSR1 handler to ppserver.py to print stats when signal is
received
Hi,
> One simple solution would be to run the script under the symlink path
> /usr/lib/pymodules/python2.6/ppworker.py.
> Then /usr/lib/pymodules/python2.6/ would be added (again) to sys.path,
> which is harmless.
FWIW that would not help apparently since
pp already does that:
DEBUG4: ['/usr/b
A related wontfix bug report in Python itself for a generic resolution:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682795
and in Cython internally this was already handled for inline
compilation (now that I am starting to recollect this issue):
http://mail.python.org/pipermail/cython-devel/2
Package: ipython
Version: 0.13.1-2
Severity: normal
Trying an exemplar %%cython snippet from
http://nbviewer.ipython.org/urls/raw.github.com/ipython/ipython/3607712653c66d63e0d7f13f073bde8c0f209ba8/docs/examples/notebooks/cython_extension.ipynb
even with minimalistic example
%%cython
cimport cyth
On Thu, 03 Jan 2013, Sandro Tosi wrote:
> thanks for your work to make numpy a better package :)
thanks for maintaining this core package ;)
> > - one assures that all for loops are secured with set -e, so if any
> > command fails, the loop fails (do not remember who pointed me to this
> > draw
nose 1.1.2-3
pn python-numpy-dbg
ii python-numpy-doc 1:1.6.2-1
-- no debconf information
>From 46bbfedb75f53f8f89ea749c60a4fc7c1ed75e3d Mon Sep 17 00:00:00 2001
From: Yaroslav Halchenko
Date: Fri, 14 Dec 2012 13:10:34 -0500
Subject: [PATCH 1/2] debian/rules: safe-guard all for loop
Package: python-virtualenv
Version: 1.7.1.2-2
Severity: normal
To check if indeed I have a fix #691244 I have tried to create python3.3
environment (using virtualenvwrapper but not sure if that is its fault --
please reassign if you are sure that it is):
$> mkvirtualenv -p /usr/bin/python3.3 pyth
On Tue, 23 Oct 2012, Matthias Klose wrote:
> please note that python3.3 comes with its own pyvenv-3.3
how could I forget about those great news...
1. btw - could you share info on what 'm' is after in
/usr/include/x86_64-linux-gnu/python3.3m
?
2. any hints on how to make nose work with 3.3 now
On Tue, 23 Oct 2012, Jakub Wilk wrote:
> >?
> It stands for "with pyMalloc".
> See: http://www.python.org/dev/peps/pep-3149/#proposal
Thank you Jakub!
> >$>
> >PYTHONPATH=/home/yoh/deb/gits/pkg-exppsy/mpi4py/install/lib/python3.3/site-packages/mpi4py
> > $HOME/python-env/python3.3/bin/python3.3
On Fri, 31 Aug 2012, Julien Cristau wrote:
> > While building a squeeze backport of new release of python-brian package
> > I just found out that there is a g++ 4.4 compatibility issue with weave
> > of scipy shipped in squeeze. Fix is trivial -- I adopted it from a
> > package in Ubuntu (links a
fixed python-scipy/0.8.0-1
thanks
On Fri, 31 Aug 2012, Adam D. Barratt wrote:
> On Fri, 2012-08-31 at 11:53 -0400, Yaroslav Halchenko wrote:
> > While building a squeeze backport of new release of python-brian package
> > I just found out that there is a g++ 4.4 compatibility i
+++ python-scipy-0.7.2+dfsg1/debian/changelog 2012-08-31 09:54:37.0
-0400
@@ -1,3 +1,11 @@
+python-scipy (0.7.2+dfsg1-1+squeeze1) stable; urgency=low
+
+ * Team upload.
+ * Patch weave-739.patch to include in blitz/*.h for weave inline
+functionality (Closes: #686353)
+
+ -- Yaroslav
Package: python-scipy
Version: 0.7.2+dfsg1-1
Severity: important
Tags: patch upstream
While building backport packages of new python-brian release I ran into a known
issue:
/usr/lib/python2.6/dist-packages/scipy/weave/blitz/blitz/mathfunc.h: In static
member function 'static long int blitz::_bz
On Tue, 21 Aug 2012, Jakub Wilk wrote:
> Control: tag -1 + wontfix
> * Dmitry Shachnev , 2012-08-21, 17:10:
> >>To allow test execution environments to discover packages which
> >>provide tests, their source packages should have a `Testsuite:`
> >>header containing `autopkgtest` (which is curren
and here we go -- was my mistake of mixing up two patch sets. If upload
of 1.7 official release to wheezy is impossible, please include the
commit 9ebe087b8bbcdeee3051e07cacd05fa07436c16e (attached, thanks Satra
once again for pointing it out) which resolves the FTBFS of
nipype.
Best regards,
> u
my reference to
,---
| e.g. I was just suggested that the fix for
| https://networkx.lanl.gov/trac/ticket/737
| which was fixed right before 1.7 release might be the one causing hard to
| reproduce (stopped failing for me again) FTBFS of nipype:
| http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=6
Package: python-networkx
Version: 1.7~rc1-2
Severity: normal
It is unfortunate that upstream's release missed Debian freeze day by
only few days, but may be at least (selected) fixes could be argued to
propagate to wheezy?
e.g. I was just suggested that the fix for
https://networkx.lanl.gov/trac
/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin"
dpkg-buildpackage -us -uc -rfakeroot
dpkg-buildpackage: source package pyamf
dpkg-buildpackage: source version 0.6.1+dfsg-3
dpkg-buildpackage: source changed by Yaroslav Halchenko
dpkg-source --before-build pyamf-0.6.1+dfsg
dpkg-buildpackage:
my guess is that it needs overrides for dh_python* calls like I did
recently for cython:
override_dh_python2:
dh_python2 -pcython
override_dh_python3:
dh_python3 -pcython3
On Sat, 28 Jul 2012, Jakub Wilk wrote:
> Package: ipython
> Version: 0.13-1
> Severity: serious
> If you rebuild
Package: python-scipy
Version: 0.10.1+dfsg1-3
Severity: serious
Tags: patch upstream
Justification: fails to build from source (but built successfully in the past)
I believe I have spotted it even before skimage FTBFSs:
https://buildd.debian.org/status/package.php?p=skimage
e.g.
https://buildd.deb
my PR to fix this bug in numpy was accepted (fix is tiny, accomplished
with unittests):
https://github.com/numpy/numpy/pull/328/files
do you think it is worth adding this patch to debian package and seeking
its acceptance to wheezy?
--
Yaroslav O. Halchenko
Postdoctoral Fellow, Department of
On Thu, 12 Jul 2012, Denis Laxalde wrote:
> >that was it -- assuring 'int' storage to be passed instead of npy_intp
> >(which is long int on s390x and int on s390) resolves this issue...
> Good to know. fitpack (interpolate) might also benefit from this.
may be -- at least there were no gcc warnin
that was it -- assuring 'int' storage to be passed instead of npy_intp
(which is long int on s390x and int on s390) resolves this issue...
now I wonder what would be the cleanest patch ;-) (also running
unittests with this fix to see how many tests get "fixed")
On Thu, 1
ee_2__dealloc__’:
> scipy/spatial/ckdtree.c:3737:17: warning: cast from pointer to integer of
> different size [-Wpointer-to-int-cast]
On Thu, 12 Jul 2012, Denis Laxalde wrote:
> tags 681270 -moreinfo
> thanks
> Yaroslav Halchenko wrote:
> >BTW -- there is a bulk o
On Thu, 12 Jul 2012, Denis Laxalde wrote:
> >BTW -- there is a bulk of possibly related unittests failures on s390x (if
> >only
> >someone was brave enough to take care about
> >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678546), e.g. (a piece
> >of diff from output on s390)...
> Ok, scip
Package: python-scipy
Version: 0.10.1+dfsg1-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Please see attached a somewhat minimalistic code to reproduce the
problem.
it fails only on s390x -- fine on s390 and any other architecture/port where
py
as
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673987#10
described, version in squeeze (1.0.1) is not effected and no action
should be done for current stable release.
or am I missing the point here?
On Mon, 09 Jul 2012, Jonathan Wiltshire wrote:
> Dear maintainer,
> Recently you fixed one
-numpy suggests:
ii gcc 4:4.7.1-1
ii gfortran 4:4.6.1-2
ii python-dev2.7.2-10
ii python-nose 1.1.2-3
ii python-numpy-dbg 1:1.6.2-1
ii python-numpy-doc 1:1.5.1-4
-- no debconf information
>From 4df244465c3db3a8e9e624d17ed2982f595e2b8a Mon Sep 17 00:00:
ok -- bug bisected to be fixed in
$> PYTHONPATH=$PWD python -c "import numpy; print numpy.__version__; print
numpy.array([('a', 1), ('b', 9.99)])"
1.7.0.dev-91f87e1
[['a' '1']
['b' '9.99']]
but unfortunat
Package: python-numpy
Version: 1:1.6.2-1
Severity: serious
Tags: upstream
I was troubleshooting pynn FTBFS
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669466
and one of the recently failed unittests was due to following regression:
$> python -c "import numpy; print numpy.__version__; print n
Package: python-scipy
Version: 0.10.1+dfsg1-3
Severity: wishlist
While troubleshooting FTBFS of statsmodels on sparc we just ran into an issue
which points to scipy (separate report will be filed whenever confirmed to be
scipy-origin). I have looked at scipy build-log [1] and besides build-depend
I wonder if smth like this would work (didn't even look what the graph
is):
python -c "import pickle, networkx as nx;
nx.to_scipy_sparse_matrix(pickle.load(open('/tmp/graph2debug.dat')))"
and see attachment
On Mon, 18 Jun 2012, Sandro Tosi wrote:
> Hello,
> can you please provide a minimal te
Package: python-networkx
Version: 1.7~rc1-1
Severity: serious
I was about to upload a fix for #664944 but the build failed due to error
while running unittests:
==
ERROR: Failure: ValueError (need more than 0 values to unpack)
--
Hi Varun,
thanks for taking care and adopting my patch. now it got accepted
upstream and I wanted to mention that they refactored few other
comparisons -- so it might be wise for Debian to adopt that patch as
well (attaching).
Cheers
On Fri, 20 Apr 2012, Debian Bug Tracking System wrote:
> You
Package: python-traits
Version: 4.0.0-1
Severity: wishlist
some times things go wrong... and it absent builds of python-traits using
python-dbg complicate not only troubleshooting bugs within traits extensions
but in any app which depends on traits since absent ctraits.so built against
python-dbg
3.2/numpy
ls: cannot access /usr/include/python3.2_d/numpy: No such file or directory
ls: cannot access /usr/include/python3.2/numpy: No such file or directory
--
=--=
Keep in touch www.onerussian.c
roblems earlier than later; 2. prepare on Debian side for the
upstream release ;-)
--
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.
Package: python-matplotlib
Version: 1.1.1~rc1-1
Severity: wishlist
Now that python3-numpy is in sid, it would be great to get python3-matplotlib
in since python3 is supported upstream AFAIK.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (
it would be a good time to prepare for
upcoming freeze assuring that dependent packages are in good shape... ?
--
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko
d'oh -- now patch is attached
On Fri, 30 Mar 2012, Yaroslav Halchenko wrote:
> patch is attached here as well
--
=--=
Keep in touch www.onerussian.com
Yaroslav H
ing the same
(1.0, nan, nan) as on x86 ... sent pull request
https://github.com/scipy/scipy/pull/187
patch is attached here as well
so next I guess is to make it return sensible values for the .fit as it did
before? ;)
On Fri, 30 Mar 2012, Yaroslav Halchenko wrote:
> well -- imho it should ha
Package: python-tornado
Version: 2.1.0-2
Severity: wishlist
haven't looked if they (tornado/test) require any internet access, but
hopefully not
e.g. for me atm tests stall at
The file descriptor underlying a FileDescriptor may be closed and ...
so it would be nice to iron them out
-- System I
Package: python-pyglet
Version: 1.1.4.dfsg-2
Severity: normal
testing new version of psychopy which uses pyglet and just randomly pressed
volume up buttong available on my thinkpad which generates following xev
information:
KeyPress event, serial 29, synthetic NO, window 0x781,
root 0xb2,
Package: python-scipy
Version: 0.9.0+dfsg1-1+b2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
I have ran into this while building pymvpa2 packages. on mips and mipsel it
times out.
I have troubleshooted it on gabrielli and I believe the followi
Package: python-scipy
Version: 0.9.0+dfsg1-1+b2
Severity: wishlist
the beast is out! ;)
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.
likely be rebased or
> deleted at some point! The final product will end up in the team svn
> when ready.
--
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenk
Hi Fernando,
Just FYI:
Thanks to Julien we now have that optional piece for ipython notebooks
available in Debian.
NB mathjax is used for rendering latex symbols in upcoming release of
ipython with notebooks. Without installed locally mathjax, which is
somewhat heavy (125MB extracted) ipy
First of all I would like to express my apologies
1. to the maintainers of the official ipython package in Debian:
$> zgrep '^ --' ~doc/ipython/changelog.Debian.gz | awk '{print $2, $3}' |
sort | uniq -c | sort -nr
29 Norbert Tretkowski
10 Jack Moffitt
7 Bernd Zeimetz
5
on.git
> But I don't give no guarantees that it won't be rebase/deleted at some
> point.
--
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko
Hi Julian and the Team,
First of all thank you for all your work for maintaining ipython and
making 0.11 available!
I wonder -- why changes toward 0.11 are not in the SVN? may be ipython
was migrated under some other VCS? (then vcs- fields should be adjusted
in debian/control), or may be it wasn
with def method.
> > warning: cpyamf/util.pyx:1121:4: Overriding cdef method with def method.
> > make[1]: *** [override_dh_auto_build] Error 1
--
=------=
Keep in touch
-incompatible-changes
http://www.tornadoweb.org/documentation/releases/v2.0.0.html
I have tentative .deb's for testing, just didn't want to attach 200KB
without your Ok ;)
Cheers
Yarik
- Forwarded message from Yaroslav Halchenko -
Date: Wed, 21 Sep 2011 19:25:09 -0400
From: Yaroslav
,
--
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http
1 - 100 of 171 matches
Mail list logo
