Thomas,
On 31 March 2016 at 18:49, Thomas Goirand wrote:
> Most of the time, you get by this doing:
> PYTHONPATH=$(CURDIR) python -m pytest tests
Awesome tip! Just stumbled up on this one when imports where changed
from relative to absolute and this tip properly fixed the matter.
Piotr,
On 31
On 04/01/2016 12:13 AM, Piotr Ożarowski wrote:
>> Most of the time, you get by this doing:
>> PYTHONPATH=$(CURDIR) python -m pytest tests
>
> this will test python2.7 only
Running tests with multiple version of Python was out of scope of my
message.
> and will most probably ignore extensions, et
[Thomas Goirand, 2016-04-02]
> > this will test python2.7 only
>
> Running tests with multiple version of Python was out of scope of my
> message.
it might be out of scope of your message, but during package's build all
interpreters ought to be tested
> > and will most probably ignore extensions
Tiago Ilieve writes:
> override_dh_auto_test:
> PYTHONPATH=$(CURDIR) py.test
> PYTHONPATH=$(CURDIR) py.test-3
This will only test the current version of Python 3. Which is OK at the
moment, there is only Python 3.5
However it was very useful to have packages run tests against Py
Package: wnpp
Severity: wishlist
Owner: Brian May
* Package name: pytest-runner
* Binary Package name : python{,3}-pytest-runner
Version : 2.7
Upstream Author : Jason R. Coombs
* URL : https://github.com/pytest-dev/pytest-runner
* License : Expat
Programming
Hi Brian,
On 2 April 2016 at 22:32, Brian May wrote:
> This will only test the current version of Python 3. Which is OK at the
> moment, there is only Python 3.5
>
> However it was very useful to have packages run tests against Python 3.5
> while Python 3.4 was still the default.
>
> I imagine th
Tiago Ilieve writes:
> I see. Actually I've removed the "override_dh_auto_test"[1] when I
> found out[2] that Pybuild can to do this by itself.
>
> Now I wonder whether this is enough to fit the use case of multiple
> Python 3 versions that you mentioned...
Yes, I believe that is sufficient. The
7 matches
Mail list logo
