Mailman 3 July 2017 - pytest-dev

Documentation proposal
by Daniele Procida Aug. 11, 2017

Aug. 11, 2017

Dear pytest developers, I have been speaking to Raphael Pierzina at EuroPython. I propose to restructure the pytest docmentation, according to this scheme <https://divio.com/blog/documentation> (the rationale for the scheme is described at length in that article). The documention already contains most of the content it requires, but I think it could be hugely improved by restructuring it. I'd also change the Sphinx theme to the RTD theme, which improves navigation. I'm happy to do the work of restructuring. I have done this for other projects (django CMS most notably). Would this be welcome? Daniele

7 8

Help testing 3.2.0 release (part 2)
by Bruno Oliveira July 31, 2017

July 31, 2017

Hi everyone, I have prepared another package for the 3.2.0 release and again it would be great if people could help test it. The package is available at: https://devpi.net/nicoddemus/dev/pytest/3.2.0 And can be installed with: pip install -U https://devpi.net/nicoddemus/dev/+f/aeb/edee851da9e58/pytest-3.2.0-py2.py3-… If we don't encounter any blocking issue like last time I pretend to release this tomorrow to PyPI. :) Cheers, Bruno.

4 6

xdist: removing boxed with degraded backward compat
by RonnyPfannschmidt July 28, 2017

July 28, 2017

hi everyone, its finally time to take and remove xdists boxed mode, in order to prepare the removal i extracted it, but that creates one clear issue, py.test messes up and has no way to protect against old xdist and boxed both registering --boxed as such users in such a situation will get a completely horrible and entirely useless error message i tried for a while to get boxed not to register its own option if xdist is there and wants it as well, but it seems impossible, in my own tests the plugin registered hook triggers after addoption so i opted to simply opt out of the own option if the xdist.boxed module is availiable -- Ronny

2 3

regendoc moved to github
by RonnyPfannschmidt July 21, 2017

July 21, 2017

Hi everyone, while addressing execnet i noted that regendoc is not getting attention by everyone even when necessary, so i moved it to github -- Ronny

1 0

execnet github import almost complete - please help and take a look
by RonnyPfannschmidt July 21, 2017

July 21, 2017

hi everyone, on https://github.com/RonnyPfannschmidt-migration-tests/execnet/ i finished a import of execnet to github i invite everyone to take another look, as i'd like to move it to pytest-dev this afternoon and put the bitbucket one to hold -- Ronny

2 1

How to deal with setup.py/setup.cfg ?
by Bastien Sevajol July 19, 2017

July 19, 2017

Hello, I use in project who contain a setup.py and setup.cfg. I configured setup.py and setup.cfg to permit execution of tests with command "python setup.py test". Structure is following: > . > ├── hello > │ └── __init__.py > ├── setup.cfg > ├── setup.py > └── tests > ├── __init__.py > ├── test_a.py > └── test_b.py setup.py is: > from setuptools import setup > > setup(name='hello', > version='0.1', > description='hello', > url='http://', > author='hello', > author_email='hello', > license='MIT', > packages=['hello'], > setup_requires=['pytest-runner'], > tests_require='pytest') and setup.cfg is: > [aliases] > test=pytest > > [tool:pytest] > addopts = tests result of "python setup.py test" is: > running pytest > running egg_info > writing dependency_links to hello.egg-info/dependency_links.txt > writing top-level names to hello.egg-info/top_level.txt > writing hello.egg-info/PKG-INFO > reading manifest file 'hello.egg-info/SOURCES.txt' > writing manifest file 'hello.egg-info/SOURCES.txt' > running build_ext > ============================ test session starts > ============================= > platform linux -- Python 3.5.3, pytest-3.1.3, py-1.4.34, pluggy-0.4.0 > rootdir: /home/bastien/Projects/test_pytest, inifile: setup.cfg > collected 2 items > > tests/test_a.py . > tests/test_b.py . > > ========================== 2 passed in 0.02 seconds > ========================== But if i want to execute only test_b with "pytest tests/test_b.py::test_b": > ============================ test session starts > ============================= > platform linux -- Python 3.5.3, pytest-3.1.3, py-1.4.34, pluggy-0.4.0 > rootdir: /home/bastien/Projects/test_pytest, inifile: setup.cfg > collected 3 items > > tests/test_a.py . > tests/test_b.py .. > > ========================== 3 passed in 0.02 seconds > ========================== All tests are collected. setup.cfg (addopts part) is the fail. I need this "addopts" part because when some developpers who work on the project create a virtualenv inside the project, pytest search into the venv folder (i add "addopts = tests" to force pytest to check only "tests" folder). How to conciliate them ? How keep a way to run test with "python setup.py test" and run a specific test with "pytest tests/test_b.py::test_b" ? Thank's, Bastien.

3 3

Help testing 3.2.0 release
by Bruno Oliveira July 14, 2017

July 14, 2017

Hi everyone, I have prepared a package for the 3.2.0 release and it would be great if people could help test it. The package is available at: https://devpi.net/nicoddemus/dev/pytest/3.2.0 And can be installed with: pip install -U https://devpi.net/nicoddemus/dev/+f/aeb/edee851da9e58/pytest-3.2.0-py2.py3-… If all goes well I plan to release it during the weekend. Cheers, Bruno.

3 7

Re: [pytest-dev] Deprecation Roadmap Wiki
by Bruno Oliveira July 12, 2017

July 12, 2017

Hi Ronny, > we should start to have a lifecycle that can start with cancel-able experiments, We could elaborate better what an "experimental" status means in practice, like how we formalized deprecations in our backward compatibility policy. []s, On Mon, Jul 10, 2017 at 7:48 PM Ronny Pfannschmidt <ich(a)ronnypfannschmidt.de> wrote: > Hi everyone, > > each of those projects shouldn't just have a deprecation roadmap, > broken features we cant kill easily (like pytest's first throw at a > warning system) > are a minefield starting with their induction > > we should start to have a lifecycle that can start with cancel-able > experiments, > simply because we are a small group of volunteers that cant run internal > a/b testing on whether an api/idea is good in the long run - we need real > world feedback of early adopters in a fashion that allows us to cancel bad > things instead of keeping them "forever" > > -- Ronny > > Am 10.07.2017 um 18:30 schrieb Bruno Oliveira: > > Hey Tyler, > > Hmmm my initial gut feeling is to keep them separate. > > Also I'm not sure if it makes sense for pluggy given that it is not even > in 1.0 yet. What do others think? > > Cheers, > Bruno. > > On Mon, Jul 10, 2017 at 12:34 PM Tyler Goodlet <tgoodlet(a)gmail.com> wrote: > >> Hey Bruno, >> >> Is it ok if I stick on stuff from pluggy (eg. __multicall__ support) or >> would you prefer I create a similar page for that in the pluggy wiki? >> >> Thanks. >> >> - Tyler >> > > > _______________________________________________ > pytest-dev mailing listpytest-dev@python.orghttps://mail.python.org/mailman/listinfo/pytest-dev > > >

1 0

Deprecation Roadmap Wiki
by Bruno Oliveira July 10, 2017

July 10, 2017

Hi everyone, I just created a page to track deprecations in our wiki: https://github.com/pytest-dev/pytest/wiki/Deprecation-Roadmap The idea is to make it clear for ourselves when we intend to remove certain features. Cheers, Bruno.

2 2

Suggestion: EuroPython pytest/tox/devpi helpdesk
by Oliver Bestwalter July 4, 2017

July 4, 2017

Hi all, EuroPython is on the horizon and they have a new thing (or at least new for me) called "helpdesk" > Helpdesk / 10 slots > Helpdesks are a great way to share your experience on a technology, by offering to help people answering their questions and solving their practical problems. You can run a helpdesk by yourself or with colleagues and friends. Each helpdesk will be open for 3 hours in total, 1.5 hours in the morning and 1.5 hours in the afternoon. People looking for help will sign up for a 30 minute slot and talk to you. There is no specific preparation needed; you just need to be proficient in the technology you run the helpdesk for. see: https://ep2017.europython.eu/en/call-for-proposals/ I would be interested to try this and volunteer to help with questions about tox mainly. Would anybody else interested in that kind of thing? If we find a handful of people that would want to do that, we could have a tox/pytest/devpi helpdesk :) Cheers, Oliver

4 13