From oliver at bestwalter.de Tue Jul 4 05:46:45 2017 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Tue, 04 Jul 2017 09:46:45 +0000 Subject: [pytest-dev] [tox-dev] Suggestion: EuroPython pytest/tox/devpi helpdesk In-Reply-To: References: <7F885631-AE64-4432-AD62-6D97ED8197AE@mozilla.com> <49073EAC-F76E-4CB1-9FBC-DC5DC8E5E93D@mozilla.com>

Message-ID: Hi all, the date for the helpdesk is tuesday from 10:30 to 12:00 and again from 14:00 to 15:30. I am also there on sunday and will stay for the sprints and do some work on tox, if you are interested to join in. See you in Rimini Oliver On Fri, 12 May 2017 at 21:33 Oliver Bestwalter wrote: > Hi all, > > I just got a mail that the helpdesk proposal was accepted. The date is not > scheduled yet. Will keep you posted. > > Cheers, > Oliver > > > On Mon, 24 Apr 2017 at 17:03 Dave Hunt wrote: > >> Unfortunately not. Might be able to attend a pytest sprint if one is >> planned, but otherwise it?ll probably be next year for me. >> >> >> On 24 Apr 2017, at 16:00, Oliver Bestwalter wrote: >> >> Hi Dave, >> >> no problem - was looking forward to see you to though. Are you attending >> Pycon US? I might be there for the sprints. >> >> Cheers, >> Oliver >> >> On Mon, 24 Apr 2017 at 15:56 Dave Hunt wrote: >> >>> Unfortunately I?ve decided not to attend EuroPython this year, so I?ll >>> need to revoke my offer to help out. Hopefully next year..! >>> >>> On 28 Mar 2017, at 09:21, Dave Hunt wrote: >>> >>> I?m thinking of coming to EuroPython, and would be happy to spend some >>> time at the helpdesk. My particular area of expertise would be the plugins >>> I maintain, but I?m sure I can also answer some pytest/tox/devpi queries >>> too. >>> >>> Cheers, >>> Dave >>> >>> On 27 Mar 2017, at 21:42, Oliver Bestwalter >>> wrote: >>> >>> 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 >>> _______________________________________________ >>> tox-dev mailing list >>> tox-dev at python.org >>> https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org/ >>> >>> >>> >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Tue Jul 4 11:33:43 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Tue, 04 Jul 2017 15:33:43 +0000 Subject: [pytest-dev] Pytest 3.1.3 Message-ID: Hi everyone, pytest 3.1.3 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at http://doc.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Antoine Legrand * Bruno Oliveira * Max Moroz * Raphael Pierzina * Ronny Pfannschmidt * Ryan Fitzpatrick Happy testing, The pytest Development Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From flub at devork.be Tue Jul 4 15:30:54 2017 From: flub at devork.be (Floris Bruynooghe) Date: Tue, 4 Jul 2017 21:30:54 +0200 Subject: [pytest-dev] [tox-dev] Re: Suggestion: EuroPython pytest/tox/devpi helpdesk In-Reply-To: References: <7F885631-AE64-4432-AD62-6D97ED8197AE@mozilla.com> <49073EAC-F76E-4CB1-9FBC-DC5DC8E5E93D@mozilla.com>

Message-ID: On 4 July 2017 at 11:46, Oliver Bestwalter wrote: > Hi all, > > the date for the helpdesk is tuesday from 10:30 to 12:00 and again from > 14:00 to 15:30. > > I am also there on sunday and will stay for the sprints and do some work on > tox, if you are interested to join in. I'll likely also run a pytest sprint alongside the tox one on Sat 15th. See you there! Floris From nicoddemus at gmail.com Mon Jul 10 10:16:43 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Mon, 10 Jul 2017 14:16:43 +0000 Subject: [pytest-dev] Deprecation Roadmap Wiki Message-ID: 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tgoodlet at gmail.com Mon Jul 10 11:34:37 2017 From: tgoodlet at gmail.com (Tyler Goodlet) Date: Mon, 10 Jul 2017 11:34:37 -0400 Subject: [pytest-dev] Deprecation Roadmap Wiki In-Reply-To: References: Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Mon Jul 10 12:30:33 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Mon, 10 Jul 2017 16:30:33 +0000 Subject: [pytest-dev] Deprecation Roadmap Wiki In-Reply-To: References:

Message-ID: 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 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Wed Jul 12 14:40:34 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Wed, 12 Jul 2017 18:40:34 +0000 Subject: [pytest-dev] Deprecation Roadmap Wiki In-Reply-To: <4bab9dec-372c-917a-4f15-6d7f82eddbbe@ronnypfannschmidt.de> References:

<4bab9dec-372c-917a-4f15-6d7f82eddbbe@ronnypfannschmidt.de> Message-ID: 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 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 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 at python.orghttps://mail.python.org/mailman/listinfo/pytest-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Thu Jul 13 18:45:09 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Thu, 13 Jul 2017 22:45:09 +0000 Subject: [pytest-dev] Help testing 3.2.0 release Message-ID: 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-none-any.whl If all goes well I plan to release it during the weekend. Cheers, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Thu Jul 13 19:40:52 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Thu, 13 Jul 2017 23:40:52 +0000 Subject: [pytest-dev] Help testing 3.2.0 release In-Reply-To: References: Message-ID: On Thu, Jul 13, 2017 at 7:45 PM Bruno Oliveira wrote: > I have prepared a package for the 3.2.0 release and it would be great if > people could help test it. > To take a look at the changes, please take a look at the CHANGELOG on the release branch: https://github.com/nicoddemus/pytest/blob/release-3.2.0/CHANGELOG.rst Cheers, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From florian.schulze at gmx.net Fri Jul 14 03:51:11 2017 From: florian.schulze at gmx.net (Florian Schulze) Date: Fri, 14 Jul 2017 09:51:11 +0200 Subject: [pytest-dev] Help testing 3.2.0 release In-Reply-To: References: Message-ID: Works fine with devpi, but ... I got the __multicall__ deprecation warning and had a very hard time to find information on how to actually fix it. In the end I found the PR that changes the docs in pytest which allowed me to change our fixture. So, if you deprecate something, please provide easy to find docs on how to actually fix it, even if the old stuff was undocumented. An example diff is often enough. Regards, Florian Schulze On 14 Jul 2017, at 0:45, Bruno Oliveira wrote: > 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-none-any.whl > > If all goes well I plan to release it during the weekend. > > Cheers, > Bruno. > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri Jul 14 08:04:12 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 14 Jul 2017 12:04:12 +0000 Subject: [pytest-dev] Help testing 3.2.0 release In-Reply-To: References:

Message-ID: Hi Florian, I definitely agree with you about making it clear what users have to do to replace deprecated functionality, which brings to attention that we could improve the bit about markers in parametrize deprecation as it stands now in the CHANGELOG. But the __multicall__ warning was not added to 3.2, it has been in place since 2015. Are you seeing this warning just now? Cheers, Bruno. On Fri, Jul 14, 2017 at 4:51 AM Florian Schulze wrote: > Works fine with devpi, but ... > > I got the __multicall__ deprecation warning and had a very hard time to > find information on how to actually fix it. In the end I found the PR that > changes the docs in pytest which allowed me to change our fixture. > > So, if you deprecate something, please provide easy to find docs on how to > actually fix it, even if the old stuff was undocumented. An example diff is > often enough. > > Regards, > Florian Schulze > > On 14 Jul 2017, at 0:45, Bruno Oliveira wrote: > > 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-none-any.whl > > If all goes well I plan to release it during the weekend. > > Cheers, > Bruno. > > _______________________________________________ > > > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From florian.schulze at gmx.net Fri Jul 14 09:02:23 2017 From: florian.schulze at gmx.net (Florian Schulze) Date: Fri, 14 Jul 2017 15:02:23 +0200 Subject: [pytest-dev] Help testing 3.2.0 release In-Reply-To: References:

Message-ID: <66806F75-E168-4D33-90CF-70C442393EA2@gmx.net> On 14 Jul 2017, at 14:04, Bruno Oliveira wrote: > But the __multicall__ warning was not added to 3.2, it has been in > place > since 2015. Are you seeing this warning just now? I saw more warnings in general. Not sure if I tried before with a pytest that included pytest-warnings, but I think I tried 3.1.x. Regards, Florian Schulze From oliver at bestwalter.de Fri Jul 14 09:34:04 2017 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Fri, 14 Jul 2017 13:34:04 +0000 Subject: [pytest-dev] Help testing 3.2.0 release In-Reply-To: References:

Message-ID: Hi Bruno, I tried to install it into an existing Python 3.6 virtualenv and it stumbled over setuptools - running it again in the same env worked then. I pasted the call and a pip freeze here in case it is of interest: https://pastebin.com/xW7KfuuN Besides from that it works fine with the projects I threw it at (tox and some private and work projects). Cheers, Oliver On Fri, 14 Jul 2017 at 14:06 Bruno Oliveira wrote: > Hi Florian, > > I definitely agree with you about making it clear what users have to do to > replace deprecated functionality, which brings to attention that we could > improve the bit about markers in parametrize deprecation as it stands now > in the CHANGELOG. > > But the __multicall__ warning was not added to 3.2, it has been in place > since 2015. Are you seeing this warning just now? > > Cheers, > Bruno. > > On Fri, Jul 14, 2017 at 4:51 AM Florian Schulze > wrote: > >> Works fine with devpi, but ... >> >> I got the __multicall__ deprecation warning and had a very hard time to >> find information on how to actually fix it. In the end I found the PR that >> changes the docs in pytest which allowed me to change our fixture. >> >> So, if you deprecate something, please provide easy to find docs on how >> to actually fix it, even if the old stuff was undocumented. An example diff >> is often enough. >> >> Regards, >> Florian Schulze >> >> On 14 Jul 2017, at 0:45, Bruno Oliveira wrote: >> >> 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-none-any.whl >> >> If all goes well I plan to release it during the weekend. >> >> Cheers, >> Bruno. >> >> _______________________________________________ >> >> >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri Jul 14 10:27:41 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 14 Jul 2017 14:27:41 +0000 Subject: [pytest-dev] Help testing 3.2.0 release In-Reply-To: <66806F75-E168-4D33-90CF-70C442393EA2@gmx.net> References:

<66806F75-E168-4D33-90CF-70C442393EA2@gmx.net> Message-ID: On Fri, Jul 14, 2017 at 10:02 AM Florian Schulze wrote: > On 14 Jul 2017, at 14:04, Bruno Oliveira wrote: > > > But the __multicall__ warning was not added to 3.2, it has been in > > place > > since 2015. Are you seeing this warning just now? > > I saw more warnings in general. Not sure if I tried before with a pytest > that included pytest-warnings, but I think I tried 3.1.x. > I see, thanks. Anyway, thanks for the reminder about making warnings more user-friendly, I don't think we have been giving this enough attention. Cheers, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri Jul 14 10:27:00 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 14 Jul 2017 14:27:00 +0000 Subject: [pytest-dev] Help testing 3.2.0 release In-Reply-To: References:

Message-ID: On Fri, Jul 14, 2017 at 10:34 AM Oliver Bestwalter wrote: > Hi Bruno, > > I tried to install it into an existing Python 3.6 virtualenv and it > stumbled over setuptools - running it again in the same env worked then. I > pasted the call and a pip freeze here in case it is of interest: > https://pastebin.com/xW7KfuuN > > Besides from that it works fine with the projects I threw it at (tox and > some private and work projects). > Thanks for testing Walter. I think the error you got is related to the virtualenv somehow. Good to know it has worked otherwise. :) Cheers, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniele at vurt.org Sat Jul 15 06:32:14 2017 From: daniele at vurt.org (Daniele Procida) Date: Sat, 15 Jul 2017 12:32:14 +0200 Subject: [pytest-dev] Documentation proposal Message-ID: <20170715103214.533927194@mail.gandi.net> Dear pytest developers, I have been speaking to Raphael Pierzina at EuroPython. I propose to restructure the pytest docmentation, according to this scheme (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 From flub at devork.be Sat Jul 15 08:09:01 2017 From: flub at devork.be (Floris Bruynooghe) Date: Sat, 15 Jul 2017 14:09:01 +0200 Subject: [pytest-dev] Documentation proposal In-Reply-To: <20170715103214.533927194@mail.gandi.net> References: <20170715103214.533927194@mail.gandi.net> Message-ID: Hi Daniele, On 15 July 2017 at 12:32, Daniele Procida wrote: > Dear pytest developers, > > I have been speaking to Raphael Pierzina at EuroPython. > > I propose to restructure the pytest docmentation, according to this scheme (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. This sounds great! From my point of view this would certainly be welcome, the navigability of our documentation is a long-standing issue which could do with improving. > I'd also change the Sphinx theme to the RTD theme, which improves navigation. I'd be a little sad to see us unified and conform to everyone else's look and to loose the logo. Which bits of navigation are you aiming to improve? Would it be possible to do with some refactoring of the contents and layout of the box on the left? We could always reach out to Tobias who did the last themes updates (IIRC) to see if he'd like fix this. > Would this be welcome? Certainly! Cheers, Floris From raphael at hackebrot.de Sat Jul 15 08:28:06 2017 From: raphael at hackebrot.de (Raphael Pierzina) Date: Sat, 15 Jul 2017 14:28:06 +0200 Subject: [pytest-dev] Documentation proposal In-Reply-To: References: <20170715103214.533927194@mail.gandi.net> Message-ID: <866CD983-7CCB-4AED-9935-497745E6DFA8@hackebrot.de> Hi Daniele, Thank you for taking iniative and getting in touch. It was great to meet you at EuroPython. Brianna Laugher, Andreas Pelme and myself worked on reorganizing the documentation during the pytest sprint in June 2016, but haven't had time to follow up on this, as far as I'm aware. Having said that, I'm happy for you to work on this. You can find out proposal in the wiki [1] and the according work-in-progess branch on GitHub [2]. Best, Raphael [1]: https://github.com/pytest-dev/pytest/wiki/Docs-refactor [2]: https://github.com/pytest-dev/pytest/tree/reorganize-docs > On 15 Jul 2017, at 14:09, Floris Bruynooghe wrote: > > Hi Daniele, > > On 15 July 2017 at 12:32, Daniele Procida wrote: >> Dear pytest developers, >> >> I have been speaking to Raphael Pierzina at EuroPython. >> >> I propose to restructure the pytest docmentation, according to this scheme (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. > > This sounds great! From my point of view this would certainly be > welcome, the navigability of our documentation is a long-standing > issue which could do with improving. > >> I'd also change the Sphinx theme to the RTD theme, which improves navigation. > > I'd be a little sad to see us unified and conform to everyone else's > look and to loose the logo. Which bits of navigation are you aiming > to improve? Would it be possible to do with some refactoring of the > contents and layout of the box on the left? We could always reach out > to Tobias who did the last themes updates (IIRC) to see if he'd like > fix this. > >> Would this be welcome? > > Certainly! > > Cheers, > Floris > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From oliver at bestwalter.de Sat Jul 15 07:35:04 2017 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Sat, 15 Jul 2017 11:35:04 +0000 Subject: [pytest-dev] Documentation proposal In-Reply-To: <20170715103214.533927194@mail.gandi.net> References: <20170715103214.533927194@mail.gandi.net> Message-ID: Hi Daniele, sounds great! I might join you later to figure out if this might also be a good idea for tox. What about changed urls though? Is there some strategy to keep old links intact or do proper redirects? Cheers, Oliver On Sat, 15 Jul 2017 at 12:32, Daniele Procida wrote: > Dear pytest developers, > > I have been speaking to Raphael Pierzina at EuroPython. > > I propose to restructure the pytest docmentation, according to this scheme > (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 > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sevajol.bastien at gmail.com Wed Jul 19 10:02:34 2017 From: sevajol.bastien at gmail.com (Bastien Sevajol) Date: Wed, 19 Jul 2017 16:02:34 +0200 Subject: [pytest-dev] How to deal with setup.py/setup.cfg ? Message-ID: <39a2b161-a5c3-0d41-b42b-ebf71d2ebb4f@gmail.com> 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. From nicoddemus at gmail.com Wed Jul 19 10:06:04 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Wed, 19 Jul 2017 14:06:04 +0000 Subject: [pytest-dev] How to deal with setup.py/setup.cfg ? In-Reply-To: <39a2b161-a5c3-0d41-b42b-ebf71d2ebb4f@gmail.com> References: <39a2b161-a5c3-0d41-b42b-ebf71d2ebb4f@gmail.com> Message-ID: Hi Bastien, I suggest to try to use the `testpaths`[1] option instead, which is tailored for just that purpose. Cheers, Bruno [1] https://docs.pytest.org/en/latest/customize.html?highlight=testpath#confval-testpaths On Wed, Jul 19, 2017 at 11:02 AM Bastien Sevajol wrote: > 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. > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Wed Jul 19 10:04:17 2017 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 19 Jul 2017 16:04:17 +0200 Subject: [pytest-dev] How to deal with setup.py/setup.cfg ? In-Reply-To: <39a2b161-a5c3-0d41-b42b-ebf71d2ebb4f@gmail.com> References: <39a2b161-a5c3-0d41-b42b-ebf71d2ebb4f@gmail.com> Message-ID: <20170719140417.5wv3h4pxlocxb6ai@hooch.localdomain> Hi, On Wed, Jul 19, 2017 at 04:02:34PM +0200, Bastien Sevajol wrote: > 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" ? Set the testpaths option instead: https://docs.pytest.org/en/latest/customize.html#confval-testpaths Florian -- https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From sevajol.bastien at gmail.com Wed Jul 19 10:21:51 2017 From: sevajol.bastien at gmail.com (Bastien Sevajol) Date: Wed, 19 Jul 2017 16:21:51 +0200 Subject: [pytest-dev] How to deal with setup.py/setup.cfg ? In-Reply-To: References: <39a2b161-a5c3-0d41-b42b-ebf71d2ebb4f@gmail.com> Message-ID: <7771c1af-7db4-5c8d-6a51-eec1bbf4f771@gmail.com> Hi, It's perfectly working, thank you a lot. Bastien. On 19/07/2017 16:06, Bruno Oliveira wrote: > Hi Bastien, > > I suggest to try to use the `testpaths`[1] option instead, which is > tailored for just that purpose. > > Cheers, > Bruno > > [1] > https://docs.pytest.org/en/latest/customize.html?highlight=testpath#confval-testpaths > > On Wed, Jul 19, 2017 at 11:02 AM Bastien Sevajol > > wrote: > > 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. > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensource at ronnypfannschmidt.de Fri Jul 21 07:35:01 2017 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Fri, 21 Jul 2017 13:35:01 +0200 Subject: [pytest-dev] execnet github import almost complete - please help and take a look Message-ID: <578b70ed-095e-48fb-cbfa-426f3628fd93@ronnypfannschmidt.de> 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 From nicoddemus at gmail.com Fri Jul 21 08:12:36 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 21 Jul 2017 12:12:36 +0000 Subject: [pytest-dev] execnet github import almost complete - please help and take a look In-Reply-To: <578b70ed-095e-48fb-cbfa-426f3628fd93@ronnypfannschmidt.de> References: <578b70ed-095e-48fb-cbfa-426f3628fd93@ronnypfannschmidt.de> Message-ID: Hi Ronny, Nice, thanks for doing this! Looks fine, except that I see 24 open issues in GH, and only 21 open issues in Bitbucket, although both contain 56 issues in all. Other than that looks crispy. Cheers, Bruno On Fri, Jul 21, 2017 at 8:35 AM RonnyPfannschmidt < opensource at ronnypfannschmidt.de> wrote: > 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 > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensource at ronnypfannschmidt.de Fri Jul 21 09:48:38 2017 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Fri, 21 Jul 2017 15:48:38 +0200 Subject: [pytest-dev] regendoc moved to github Message-ID: <06d6731a-f739-9540-4800-b09ff795c131@ronnypfannschmidt.de> 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 From opensource at ronnypfannschmidt.de Fri Jul 28 11:49:48 2017 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Fri, 28 Jul 2017 17:49:48 +0200 Subject: [pytest-dev] xdist: removing boxed with degraded backward compat Message-ID: <60febbe5-64fd-7947-17f9-c24a52c8c000@ronnypfannschmidt.de> 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 From nicoddemus at gmail.com Fri Jul 28 11:59:08 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 28 Jul 2017 15:59:08 +0000 Subject: [pytest-dev] xdist: removing boxed with degraded backward compat In-Reply-To: <60febbe5-64fd-7947-17f9-c24a52c8c000@ronnypfannschmidt.de> References: <60febbe5-64fd-7947-17f9-c24a52c8c000@ronnypfannschmidt.de> Message-ID: Hey Ronny, Does this new "pytest-boxed"(?) plugin depends on pytest-xdist? If it does I think it is just a matter of pinning that dependency as requiring a minimum of pytest-xdist >= 2 so users will get a version conflict error if they try to install incompatible versions (I'm assuming the pytest-xdist release without --boxed will be 2.0). Cheers, On Fri, Jul 28, 2017 at 12:50 PM RonnyPfannschmidt < opensource at ronnypfannschmidt.de> wrote: > 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 > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensource at ronnypfannschmidt.de Fri Jul 28 12:00:35 2017 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Fri, 28 Jul 2017 18:00:35 +0200 Subject: [pytest-dev] xdist: removing boxed with degraded backward compat In-Reply-To: References: <60febbe5-64fd-7947-17f9-c24a52c8c000@ronnypfannschmidt.de> Message-ID: <257d6931-a24a-4d98-9c0f-a6c7618a2b38@ronnypfannschmidt.de> Hi Bruno, its the other way around boxed jsut takes the fork using mess out of xdist so i can drop that code -- Ronny Am 28.07.2017 um 17:59 schrieb Bruno Oliveira: > Hey Ronny, > > Does this new "pytest-boxed"(?) plugin depends on pytest-xdist? If it > does I think it is just a matter of pinning that dependency as requiring > a minimum of pytest-xdist >= 2 so users will get a version conflict > error if they try to install incompatible versions (I'm assuming the > pytest-xdist release without --boxed will be 2.0). > > Cheers, > > On Fri, Jul 28, 2017 at 12:50 PM RonnyPfannschmidt > > wrote: > > 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 > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > From nicoddemus at gmail.com Fri Jul 28 13:04:03 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 28 Jul 2017 17:04:03 +0000 Subject: [pytest-dev] xdist: removing boxed with degraded backward compat In-Reply-To: <257d6931-a24a-4d98-9c0f-a6c7618a2b38@ronnypfannschmidt.de> References: <60febbe5-64fd-7947-17f9-c24a52c8c000@ronnypfannschmidt.de> <257d6931-a24a-4d98-9c0f-a6c7618a2b38@ronnypfannschmidt.de> Message-ID: But will pytest-xdist still keep the option around? IIUC the conflict will only happen if the user is using the new pytest-boxed together with an old pytest-xdist version, correct? Another idea: how about naming it something else? pytest-forked (heh)? That would be a completely separate plugin with a separate option (--forked). Cheers, On Fri, Jul 28, 2017 at 1:00 PM RonnyPfannschmidt < opensource at ronnypfannschmidt.de> wrote: > Hi Bruno, > > its the other way around boxed jsut takes the fork using mess out of > xdist so i can drop that code > > -- Ronny > > > Am 28.07.2017 um 17:59 schrieb Bruno Oliveira: > > Hey Ronny, > > > > Does this new "pytest-boxed"(?) plugin depends on pytest-xdist? If it > > does I think it is just a matter of pinning that dependency as requiring > > a minimum of pytest-xdist >= 2 so users will get a version conflict > > error if they try to install incompatible versions (I'm assuming the > > pytest-xdist release without --boxed will be 2.0). > > > > Cheers, > > > > On Fri, Jul 28, 2017 at 12:50 PM RonnyPfannschmidt > > > > wrote: > > > > 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 > > > > _______________________________________________ > > pytest-dev mailing list > > pytest-dev at python.org > > https://mail.python.org/mailman/listinfo/pytest-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Mon Jul 31 07:31:12 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Mon, 31 Jul 2017 11:31:12 +0000 Subject: [pytest-dev] Help testing 3.2.0 release (part 2) Message-ID: 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-none-any.whl If we don't encounter any blocking issue like last time I pretend to release this tomorrow to PyPI. :) Cheers, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Mon Jul 31 07:43:56 2017 From: me at the-compiler.org (Florian Bruhin) Date: Mon, 31 Jul 2017 13:43:56 +0200 Subject: [pytest-dev] Help testing 3.2.0 release (part 2) In-Reply-To: References: Message-ID: <20170731114356.eiw4mdhda7hcwmra@hooch.localdomain> Hey Bruno, On Mon, Jul 31, 2017 at 11:31:12AM +0000, Bruno Oliveira wrote: > I have prepared another package for the 3.2.0 release and again it would be > great if people could help test it. Thanks! Seems to work fine with qutebrowser this time :) > 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-none-any.whl I had to do: pip install --no-cache-dir -U https://devpi.net/nicoddemus/dev/+f/e50/b5a054e0007ca/pytest-3.2.0-py2.py3-none-any.whl It looks like the URL changed when you re-uploaded it, and I had to use --no-cache-dir to convince pip to re-download it. (btw - I feel like everyone's life would be easier if we'd just push release canditates to PyPI which are installable with --pre. Then we can also simply do an rc2 in cases like this) Florian -- https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From nicoddemus at gmail.com Mon Jul 31 07:59:32 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Mon, 31 Jul 2017 11:59:32 +0000 Subject: [pytest-dev] Help testing 3.2.0 release (part 2) In-Reply-To: <20170731114356.eiw4mdhda7hcwmra@hooch.localdomain> References: <20170731114356.eiw4mdhda7hcwmra@hooch.localdomain> Message-ID: On Mon, Jul 31, 2017 at 8:44 AM Florian Bruhin wrote: > Thanks! Seems to work fine with qutebrowser this time :) > Glad to know, thanks! > > > 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-none-any.whl > > I had to do: > > pip install --no-cache-dir -U > https://devpi.net/nicoddemus/dev/+f/e50/b5a054e0007ca/pytest-3.2.0-py2.py3-none-any.whl > > It looks like the URL changed when you re-uploaded it, and I had to use > --no-cache-dir to convince pip to re-download it. > Oops yep my bad, I shamelessly copied my previous email and just edited it a bit. :P (btw - I feel like everyone's life would be easier if we'd just push > release canditates to PyPI which are installable with --pre. Then we can > also simply do an rc2 in cases like this) > Hmmm that does sound like a good idea at first. Two things came to my mind though: 1. Doesn't tox install dependencies with --pre? If that's true then tox users would install the release candidate by default. 2. Our release process doesn't account for it today, so we would have to review it (specially changelog wise I think). Thanks again for testing it out! Cheers. Bruno > Florian > > -- > https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) > GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc > I love long mails! | https://email.is-not-s.ms/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Mon Jul 31 08:03:19 2017 From: me at the-compiler.org (Florian Bruhin) Date: Mon, 31 Jul 2017 14:03:19 +0200 Subject: [pytest-dev] Doing pre-releases (was: Re: Help testing 3.2.0 release (part 2)) In-Reply-To: References: <20170731114356.eiw4mdhda7hcwmra@hooch.localdomain> Message-ID: <20170731120318.4cbyv2hjtusir6ho@hooch.localdomain> On Mon, Jul 31, 2017 at 11:59:32AM +0000, Bruno Oliveira wrote: > > (btw - I feel like everyone's life would be easier if we'd just push > > release canditates to PyPI which are installable with --pre. Then we can > > also simply do an rc2 in cases like this) > > > > Hmmm that does sound like a good idea at first. Two things came to my mind > though: > > 1. Doesn't tox install dependencies with --pre? If that's true then tox > users would install the release candidate by default. Not by default, only when you tell it to: http://tox.readthedocs.io/en/latest/config.html#confval-pip_pre=True%7CFalse(default) > 2. Our release process doesn't account for it today, so we would have to > review it (specially changelog wise I think). What would change about changelogs? You could still just finalize the changelog with the final release, I think. Florian -- https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From rpfannsc at redhat.com Mon Jul 31 08:09:45 2017 From: rpfannsc at redhat.com (Ronny Pfannschmidt) Date: Mon, 31 Jul 2017 14:09:45 +0200 Subject: [pytest-dev] Doing pre-releases (was: Re: Help testing 3.2.0 release (part 2)) In-Reply-To: <20170731120318.4cbyv2hjtusir6ho@hooch.localdomain> References: <20170731114356.eiw4mdhda7hcwmra@hooch.localdomain> <20170731120318.4cbyv2hjtusir6ho@hooch.localdomain> Message-ID: we should mirror borgbackup in that regard https://borgbackup.readthedocs.io/en/stable/changes.html#changelog materializes releases candidates we can do a automation around that as well i wanted to propose adding a travis deploy that uploads release proposals with materialized changelogs anyway so that doing a release would be as simple as doing a merge form the ui 2017-07-31 14:03 GMT+02:00 Florian Bruhin : > On Mon, Jul 31, 2017 at 11:59:32AM +0000, Bruno Oliveira wrote: > > > (btw - I feel like everyone's life would be easier if we'd just push > > > release canditates to PyPI which are installable with --pre. Then we > can > > > also simply do an rc2 in cases like this) > > > > > > > Hmmm that does sound like a good idea at first. Two things came to my > mind > > though: > > > > 1. Doesn't tox install dependencies with --pre? If that's true then tox > > users would install the release candidate by default. > > Not by default, only when you tell it to: > http://tox.readthedocs.io/en/latest/config.html#confval- > pip_pre=True%7CFalse(default) > > > > 2. Our release process doesn't account for it today, so we would have to > > review it (specially changelog wise I think). > > What would change about changelogs? You could still just finalize the > changelog with the final release, I think. > > Florian > > -- > https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP) > GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc > I love long mails! | https://email.is-not-s.ms/ > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -- Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander -------------- next part -------------- An HTML attachment was scrubbed... URL: From florian.schulze at gmx.net Mon Jul 31 09:40:12 2017 From: florian.schulze at gmx.net (Florian Schulze) Date: Mon, 31 Jul 2017 15:40:12 +0200 Subject: [pytest-dev] Help testing 3.2.0 release (part 2) In-Reply-To: <20170731114356.eiw4mdhda7hcwmra@hooch.localdomain> References: <20170731114356.eiw4mdhda7hcwmra@hooch.localdomain> Message-ID: <01E4CD06-4DB2-417D-B099-1B56E1AB991E@gmx.net> > I had to do: > > pip install --no-cache-dir -U > https://devpi.net/nicoddemus/dev/+f/e50/b5a054e0007ca/pytest-3.2.0-py2.py3-none-any.whl This works with devpi tests as well. Regards, Florian Schulze From nicoddemus at gmail.com Mon Jul 31 09:40:57 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Mon, 31 Jul 2017 13:40:57 +0000 Subject: [pytest-dev] Help testing 3.2.0 release (part 2) In-Reply-To: <01E4CD06-4DB2-417D-B099-1B56E1AB991E@gmx.net> References: <20170731114356.eiw4mdhda7hcwmra@hooch.localdomain> <01E4CD06-4DB2-417D-B099-1B56E1AB991E@gmx.net> Message-ID: On Mon, Jul 31, 2017 at 10:40 AM Florian Schulze wrote: > > I had to do: > > > > pip install --no-cache-dir -U > > > https://devpi.net/nicoddemus/dev/+f/e50/b5a054e0007ca/pytest-3.2.0-py2.py3-none-any.whl > > This works with devpi tests as well. > Thanks Florian! Cheers, Bruno -------------- next part -------------- An HTML attachment was scrubbed... URL: