On Jan 22 2017, Santiago Vila <sanv...@unex.es> wrote:
> On Sat, Jan 21, 2017 at 04:12:28PM -0800, Nikolaus Rath wrote:
>
>> Are you able to reproduce this with Python 3.5?
>
> I don't know. I'm just building the package from source.
>
> The package currently build-depends on both python-all-dev and
> python3-all-dev.
>
> By "trying with Python 3.5" you mean removing the build-dependency on
> python-all-dev?
Sorry, this was a little terse. The build process runs with unit tests
with all available Python versions, starting with 2.x. However, it
aborts on the first failed test. I was wondering if in any of your
builds it ever made it through the 2.7 tests and then failed when
testing with 3.x.
You could force this behavior by removing the "-x" from test/pytest.ini
(in this case it attempts to run all tests). Removing the build-depends
may work as well, I'm not 100% sure.
Best,
Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
