Hi Piotr,
On Sat, Mar 15, 2014 at 12:52:41PM +0100, Piotr Ożarowski wrote:
pybuild takes care of distutils cannot find files it build in previous
step and has to build them again problem. I just checked
python-biopython and all .so files are in the right location
(yey pybuild! :).
The
Hi Éric,
On Fri, Mar 14, 2014 at 07:15:26PM -0400, Éric Araujo wrote:
There are two ways to fix that: either make distutils build the
extensions alongside the Python modules, or make the test import all
code from the build directory. I’m surprised that this isn’t a
common issue for PMPT.
Hi,
I tried the first solution and did not see a difference in tests:
both times, 223 tests were run successfully. I’d like to reproduce
the errors you mention to be sure that any change I make is actually
a fix.
I guess this is the solution since if the C modules are not found the
test
On 15.03.2014 00:15, Éric Araujo wrote:
Hello,
I got the code and the debian directory. I confirmed that extension
modules are in the build directory, not alongside the Python modules, so
they can’t be imported from tests.
There are two ways to fix that: either make distutils build
[Éric Araujo, 2014-03-15]
Hi,
I tried the first solution and did not see a difference in tests:
both times, 223 tests were run successfully. I’d like to reproduce
the errors you mention to be sure that any change I make is actually
a fix.
I guess this is the solution since if the C
On Wed, Mar 12, 2014 at 01:20:38AM -0400, Éric Araujo wrote:
Le 05/03/2014 10:31, Andreas Tille a écrit :
I have noted another problem: I worked a bit
on the tests and noticed that those tests that are including compiled C
code are failing. Is there anything in addition I need to do to make
Hello,
I got the code and the debian directory. I confirmed that extension
modules are in the build directory, not alongside the Python modules, so
they can’t be imported from tests.
There are two ways to fix that: either make distutils build the
extensions alongside the Python
Hello,
Le 05/03/2014 10:31, Andreas Tille a écrit :
I have noted another problem: I worked a bit
on the tests and noticed that those tests that are including compiled C
code are failing. Is there anything in addition I need to do to make
the C object code visible to the Python modules?
Can
Hi again
On Tue, Mar 04, 2014 at 07:18:08PM +0100, Andreas Tille wrote:
you can force pybuild to move BioSQL files to a different location
(hint: --ext-dest-dir --ext-pattern or equivalent PYBUILD_* vars)
but IMO it's cleaner to use *.install files for that
Hmmm, you say *.install files
Hi,
I tried to work on python-biopython which according to authors request
supports also Python3 and so I tried to put this into the packaging at
svn://anonscm.debian.org/debian-med/trunk/packages/python-biopython/trunk/
The problem is that I seem to have messed up the debian/*.install files
[Andreas Tille, 2014-03-04]
I tried to work on python-biopython which according to authors request
supports also Python3 and so I tried to put this into the packaging at
svn://anonscm.debian.org/debian-med/trunk/packages/python-biopython/trunk/
^ this one is not anonymous, this one is:
On Mar 04, 2014, at 05:26 PM, Piotr Ożarowski wrote:
PS please add X-Python-Version: = 3.3 in debian/control, this module
doesn't work with 3.2
Oops. Shouldn't that be X-Python3-Version: = 3.3 ? :)
-Barry
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of
Answering the question Piotr didn't answer:
On Tue, Mar 4, 2014 at 4:59 PM, Andreas Tille andr...@an3as.eu wrote:
1. numpy
While
dh_numpy -ppython-biopython
does create the proper Dependencies in the python-biopython package
dh_numpy3 -ppython3-biopython
Hi,
On Tue, Mar 04, 2014 at 05:26:51PM +0100, Piotr Ożarowski wrote:
[Andreas Tille, 2014-03-04]
I tried to work on python-biopython which according to authors request
supports also Python3 and so I tried to put this into the packaging at
14 matches
Mail list logo
