Re: [pytest-dev] Testing pytest releases using devpi and CI servers

h we could securely encrypt into the .travis.yml file itself. This way documentation could be automatically generated and uploaded. I think Ronny has a similar idea. Cheers, Bruno. > > Greetings from sf, holger > > > > > > > > On January 14, 2016 9:15:37 PM PST, Flo

[pytest-dev] Testing pytest releases using devpi and CI servers

Hi guys, Recently we discussed how one could test pytest release packages using devpi in multiple machines, before the release is made official. I created a small repository[1] which only contains appveyor and travis scripts which simply use "devpi test" to test and publish results for the

Re: [pytest-dev] More flexibility on test function naming conventions

Ernesto, Nice that you found the solution. Just to note that the documentation seems correct: .. confval:: python_functions One or more name prefixes or glob-patterns determining which test functions and methods are considered tests. Cheers, Bruno. On Sat, Jan 9, 2016 at 8:16 AM

[pytest-dev] pytest.org down?

Hi guys, Is pytest.org down? To me it lands on a “Go Daddy” domain sales site… []s, ​ ___ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev

Re: [pytest-dev] pytest sprint 2016 / getting started

On Thu, Jan 7, 2016 at 8:40 AM holger krekel wrote: > let's try to find out if we can make a pytest sprint happen in 2016. > Excellent, my first pytest sprint (hopefully). :D > Location: somewhere around Freiburg, black forest, Germany. > Date ranges: > > 20-26th

Re: [pytest-dev] Dropping python 2.6 support in pytest 2.9

On Sun, Jan 3, 2016 at 3:59 PM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Hi everyone, > > Since 2.6 is eol since a while now I'd like to drop support for it in > pytest 2.9 > As I said on the thread for this issue, I'm +0 on it. :) Cheers,

Re: [pytest-dev] Paid contract desired/bountysource label on gh ?

I think it is a good idea to have bounty labels... having an official channel for people to explicitly offer bounties would be nice. On Fri, Jan 1, 2016 at 3:20 PM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote: > Hi all, > > While grooming I stumbled upon issues where Holger

Re: [pytest-dev] State of pytest-bdd

On Wed, Dec 16, 2015 at 7:34 AM Florian Bruhin wrote: > It seems Anatoly Bubenkov isn't very active anymore on the plugin, and > Oleg Pidsadnyi who has answered to some of the issues I opened seems > very busy as well. > > I'd like to get that plugin in shape a bit more

Re: [pytest-dev] pytest hangout meeting minutes

Thanks Florian for taking the time to create this transcript! :) On Tue, Dec 15, 2015 at 7:42 PM Florian Bruhin wrote: > We had an (experimental) Google Hangout meeting with some core > developers today - here are the notes I took, completely unedited > because I want to

Re: [pytest-dev] Parametrized scope question

Hi, Another option is to use fixtures to obtain the values, since fixtures can be overwritten in subclasses: import pytest class Base: @pytest.fixture(scope='class') def param(self): assert 0 @pytest.yield_fixture(scope='class') def fix(self, param, request):

Re: [pytest-dev] thanking for PRs?

On Fri, Dec 11, 2015 at 12:30 PM holger krekel wrote: > > I was wondering about the practise to have PR authors add themselves > to AUTHORS and CHANGELOG. The latter particularly is a bit odd, i.e. > to thank yourself for submitting a PR. What do you all think about >

[pytest-dev] pytest 2.8.5 released

at: http://pytest.org As usual, you can upgrade from pypi via:: pip install -U pytest Thanks to all who contributed to this release, among them: Alex Gaynor aselus-hub Bruno Oliveira Ronny Pfannschmidt Happy testing, The py.test Development Team 2.8.5 (compared to 2.8.4

Re: [pytest-dev] pytest plugin pytest-session_to_file

Hi Richard, Thanks for the pointer. We have to integrate the plugin_index script into the gendoc Makefile target. Cheers, Bruno. On Thu, Oct 1, 2015 at 12:51 PM Richard Vézina wrote: > Hello, > > I just create this : > >

Re: [pytest-dev] maintaining a synced git fork easily?

On Mon, Sep 28, 2015 at 7:26 AM Florian Bruhin wrote: > I usually have the following workflow when I contribute to projects: > I have the exact workflow as Florian. :) I would only add that you can create your branches based directly on the upstream: $ git checkout -b

Re: [pytest-dev] pytest-2.8.1 monday?

Hey, I think we should focus in fixing regressions that caused people to pin down pytest back to 2.7.3. Looking at the issues it seems we got all of those. Backward compatibility issues which would be nice to have on this release: https://github.com/pytest-dev/pytest/issues/1037

Re: [pytest-dev] pytest-capturelog status/merging to core?

On Fri, Sep 25, 2015 at 9:03 AM Florian Bruhin wrote: > As I said there, I'm actually not sure if it should be merged, or at > least not yet - it's finally starting to have some bugfixes and > features compared to capturelog, and I plan to contribute some more > stuff I

Re: [pytest-dev] pytest-2.8 / new branches

On Mon, Sep 21, 2015 at 9:40 AM holger krekel wrote: > So what about these branches: > > - master: bugfixes (for current latest pytest release) which will > usually be released in a new micro revision. > > - features: will result in a new minor or major revision. > > This

Re: [pytest-dev] pytest-2.8 / new branches

On Mon, Sep 21, 2015 at 9:10 AM holger krekel wrote: > Hey all, > > just changed CONTRIBUTING to reflect the pytest-2.8 reality: > > https://github.com/pytest-dev/pytest/pull/1038 > > In it i suggest we use a "2.8.X" branch for bugfixes of the 2.8 series > and master for

Re: [pytest-dev] [TIP] pytest 2.8

t; chokes? > I have the same results here on Windows, FWIW. Cheers, Bruno. On Fri, Sep 18, 2015 at 22:09 +, Bruno Oliveira wrote: > > Hi all, > > > > pytest 2.8 has been released to pypi, with significant bug-fixes and > > features. > > > > In case

Re: [pytest-dev] Releases

exists: > '/tmp/regendoc-exec-GzZfWJ/nonpython.rst-76/nonpython' > > Does it work for you? > Hmm I get the same error when running on a ubuntu virtualbox... perhaps Ronny can chip in? Cheers, Bruno. On Tue, Sep 15, 2015 at 14:41 +, Bruno Oliveira wrote: > > On Tue, Se

Re: [pytest-dev] Disabling third-party application access on GitHub

So you had to actually revoke it, like you said earlier. :) Nice, thank you very much! Cheers, On Sat, Sep 12, 2015 at 6:57 PM Florian Bruhin <m...@the-compiler.org> wrote: > * Bruno Oliveira <nicodde...@gmail.com> [2015-09-12 21:45:02 +]: > > Hmm it seems that afte

Re: [pytest-dev] Disabling third-party application access on GitHub

I did the same for Travis, hopefully everything is working now. :) Cheers, On Sat, Sep 12, 2015 at 6:59 PM Bruno Oliveira <nicodde...@gmail.com> wrote: > So you had to actually revoke it, like you said earlier. :) > > Nice, thank you very much! > > Cheers, > > On S

Re: [pytest-dev] Disabling third-party application access on GitHub

/pytest-dev/settings/oauth_application_policy) or in AppVeyor. Does anyone have any tips how to do this? I was trying to add pytest-faulthandler to AppVeyor, if it is relevant. Cheers, On Sat, Sep 12, 2015 at 10:54 AM Bruno Oliveira <nicodde...@gmail.com> wrote: > On Sat, Sep 12, 2015

Re: [pytest-dev] Disabling third-party application access on GitHub

On Sat, Sep 12, 2015 at 10:36 AM Florian Bruhin wrote: > * Florian Bruhin [2015-09-10 17:05:36 +0200]: > Who has the credentials for the pytestbot account? Bruno? I think > you'll need to remove and re-add them, and then a pytest-dev owner > needs

Re: [pytest-dev] Releases

Hi Holger, Glad to have you back. :) The main points holding back 2.8 I think are: * vendoring pluggy (https://github.com/pytest-dev/pytest/pull/959) * merge pytest-cache into core ( https://github.com/pytest-dev/pytest/pull/828) Cheers, Bruno. On Mon, Sep 7, 2015 at 5:16 AM holger krekel

Re: [pytest-dev] Releases

On Tue, Aug 25, 2015 at 12:34 PM Floris Bruynooghe f...@devork.be wrote: On 25 August 2015 at 14:10, Floris Bruynooghe f...@devork.be wrote: On 25 August 2015 at 12:58, Bruno Oliveira nicodde...@gmail.com wrote: How about: * Create a script which fetches the latest pluggy version

Re: [pytest-dev] Releases

Hi, I also think we should release 2.8 directly. There are a couple of issues/PRs that should go into 2.8, IMO: - Merge pytest-cache into core ( https://github.com/pytest-dev/pytest/pull/828); I think Ronny is working on this; - Release pytest-xdist 1.13, so we can merge non-zero exit code if

[pytest-dev] devpi channel for Travis CI testing of pytest-dev/pytest

Hi everyone, Currently we use Holger's private channel (https://devpi.net/hpk/dev) to obtain packages for testing on Travis. How about if we create a pytest-dev user on devpi.net which would be the official package source for continuous integration of pytest-dev/pytest? This would allow other

Re: [pytest-dev] Move Cookiecutter template for Pytest plugins to Org

Definitely +1. :) Cheers, On Wed, Jul 29, 2015 at 10:41 AM Raphael Pierzina raph...@hackebrot.de wrote: Hi there, Andreas and I have been working on a Cookiecutter template for Pytest plugins during the EuroPython 2015 sprints. I think it is ready to be moved to the pytest-dev

Re: [pytest-dev] devpi.net

Thanks Florian, No rush, just thought I would mention here in the list in case nobody has noticed yet. :) Cheers, On Mon, Jul 13, 2015 at 8:31 AM Florian Schulze m...@florian-schulze.net wrote: On 13 Jul 2015, at 13:27, Bruno Oliveira wrote: Hi, I noticed that devpi.net is down, so

Re: [pytest-dev] github push notification / pytest channel

it out. Cheers, On Fri, Jun 19, 2015 at 7:35 AM Bruno Oliveira nicodde...@gmail.com wrote: On Fri, Jun 19, 2015 at 5:25 AM Florian Bruhin m...@the-compiler.org wrote: We could also set up Travis IRC notifications so we notice when things would break for some reason: http://docs.travis

Re: [pytest-dev] github push notification / pytest channel

On Fri, Jun 19, 2015 at 5:25 AM Florian Bruhin m...@the-compiler.org wrote: We could also set up Travis IRC notifications so we notice when things would break for some reason: http://docs.travis-ci.com/user/notifications/#IRC-notification Just merged Florian's PR which does that:

Re: [pytest-dev] plugins/pytest-qt and cx_Freeze

Hi Florian, I have this problem as well and was trying to find a better solution before bringing up this issue, but let me share my solution so far. The problem is that the mechanism for plugin discovered used by pytest (setupttools entry points) doesn't work with frozen executables so pytest

Re: [pytest-dev] plugins/pytest-qt and cx_Freeze

Nice, thanks for sharing! :) Cheers, On Thu, Jun 18, 2015 at 12:21 PM Florian Bruhin m...@the-compiler.org wrote: Another solution would be to explicitly pass the plugin in the command line using `-p pytestq.plugin`. Sorry for the double-post - I found an (IMHO) slightly better solution

Re: [pytest-dev] 2.8.0 release plan? 2.7.2?

On Thu, Jun 18, 2015 at 2:47 AM holger krekel hol...@merlinux.eu wrote: On Wed, Jun 17, 2015 at 22:06 -0700, Floris Bruynooghe wrote: I think Ronny had some 2.7.2 plans as well or wanted it soon for some reason? pytest-cache integration into the core perhaps? Maybe we can just aim for

Re: [pytest-dev] Trove Classifier for pytest plugins

On Thu, Jun 18, 2015 at 6:49 PM Laura Creighton l...@openend.se wrote: So I think this is a great idea. I see no downside at all. What would it be? People commented on the issue I posted supporting this idea, so I moved this forward by requesting to add a new Trove classifier here:

[pytest-dev] Trove Classifier for pytest plugins

Hi, Recently Jason R. Coombs proposed to create an specific trove classifier for pytest plugins: https://github.com/pytest-dev/plugincompat/issues/16 One benefit is that it would make it easier for people to find pytest plugins, as the recommended approach of searching for pytest- named

[pytest-dev] 2.8.0 release plan? 2.7.2?

Hi, Do we have an idea of when we would like have a 2.8.0 release, or at least what we would like to see in the new version? And about 2.7.2? I see there are a couple of fixes that are in master but should be backported to pytest-2.7 branch before making a 2.7.2 release. Cheers,

Re: [pytest-dev] Pytest migration to GitHub

! Cheers, On Mon, Jun 15, 2015 at 5:31 PM Bruno Oliveira nicodde...@gmail.com wrote: Hi everyone, The migration process has started now. I will send an email once the first steps are complete. Cheers, On Mon, Jun 15, 2015 at 9:59 AM Bruno Oliveira nicodde...@gmail.com wrote: Hi

[pytest-dev] ANN: pytest development has moved to GitHub

Hi, pytest development has moved to GitHub at https://github.com/pytest-dev/pytest. All issues have been migrated as well. For those interested, the move was the result of requests from several users and some pytest-core developers, and the reasons for the move can be found in this issue:

Re: [pytest-dev] Pytest migration to GitHub

Bruno Oliveira nicodde...@gmail.com wrote: Hi everyone, We have our new repository ready: https://github.com/pytest-dev/pytest Issues and commits may now continue on the new repository. The few remaining tasks to fully complete the move are listed here: https://github.com/pytest-dev/pytest

Re: [pytest-dev] moving to git / issues?

github issue? thanks again for the work. holger On Thu, Jun 11, 2015 at 00:10 +, Bruno Oliveira wrote: Hi Floris, What happens to existing pull requests? If we don't merge them before Sat we have to convert them to git ourself and re-make the PR? Yes, as there are few PRs

Re: [pytest-dev] moving to git / issues?

they will be!). Does that sound reasonable? IMO yes, unless others disagree. Cheers, On Wed, Jun 10, 2015 at 8:47 PM Floris Bruynooghe f...@devork.be wrote: On 10 June 2015 at 14:07, Bruno Oliveira nicodde...@gmail.com wrote: Hi guys, Just wanted to know if everyone is OK with migrating pytest

Re: [pytest-dev] moving to git / issues?

...@gmail.com wrote: Sounds like a good plan! It's easier to implement it by one person I think and that person is you! :) On 05:46, Sat, Jun 6, 2015 Bruno Oliveira nicodde...@gmail.com wrote: Implemented the last suggestions by Florian, I think issue migration looks good now. What would

Re: [pytest-dev] moving to git / issues?

On Fri, Jun 5, 2015 at 1:19 AM Florian Bruhin m...@the-compiler.org wrote: When doing the final migration, which user should we use? I suggest creating a new user for the migration so it's immediately apparent that's not the real issue author. For example, a

Re: [pytest-dev] moving to git / issues?

, 2015 at 3:48 PM holger krekel hol...@merlinux.eu wrote: On Wed, Jun 03, 2015 at 16:12 +, Bruno Oliveira wrote: Can you please enable issues (so meta!) for the repo? Done! :) Then I suggest to continue discussions there, so people interested in it can watch the repo, and everyone

Re: [pytest-dev] moving to git / issues?

:01 PM Florian Bruhin m...@the-compiler.org wrote: * Bruno Oliveira nicodde...@gmail.com [2015-06-03 15:59:17 +]: For the script, or for a playground to do the migration? I meant for the script... I agree that everyone should use their own playground for testing it. Added you

Re: [pytest-dev] moving to git / issues?

, we can discuss the next steps in detail. On Wed, Jun 3, 2015 at 12:51 PM Florian Bruhin m...@the-compiler.org wrote: * Bruno Oliveira nicodde...@gmail.com [2015-06-03 15:37:24 +]: I forked the script and fixed that particular issue: https://github.com/nicoddemus/bitbucket_issue_migration

Re: [pytest-dev] moving to git / issues?

I forked the script and fixed that particular issue: https://github.com/nicoddemus/bitbucket_issue_migration/ Right now I'm hitting another error around 8th issue: Created 8 of 762 issues Traceback (most recent call last): File migrate.py, line 302, in module print Comments,

Re: [pytest-dev] pytest-2.7.1 / bugs? / release?

Hi, I find that a bug sprint is a good idea, count me in. Cheers, On Sat, Apr 18, 2015 at 4:17 AM, holger krekel hol...@merlinux.eu wrote: Hi all, what about we try to do a little pytest-2.7.1 release in like 10 days or so? Two suggestions for that: - everyone picks and fixes (at

Re: [pytest-dev] New plugin for generating HTML report (and request for help)

Hi Dave, Congratulations on this initiative to separate this functionality into a separate plugin, it seems very useful! :) One way to allow other plugins to interact with yours is by defining your own hooks. Pytest-xdist does this[1], and as an example, the builtin hook pytest_report_header[2]

[pytest-dev] yield_fixture experimental status

Hi all, yield_fixture is still listed as experimental in the docs ( http://pytest.org/latest/yieldfixture.html). Do we still want to discuss/change it, or should we drop the experimental status from the documentation? Myself love it, and use it almost exclusively when I want to write a fixture

[pytest-dev] Move pytest-faulthandler to pytest-dev@github

Hi all, I would to like to know if there are any objections to moving the pytest-faulthandler (https://github.com/nicoddemus/pytest-faulthandler) plugin to the pytest-dev@github organization? Cheers,___ pytest-dev mailing list pytest-dev@python.org

Re: [pytest-dev] moving pytest-timeout to pytest-dev

+1, certainly :) Em 31/03/2015 20:38, Anatoly Bubenkov bubenk...@gmail.com escreveu: +1 On 1 April 2015 at 00:57, Floris Bruynooghe f...@devork.be wrote: Hi all, If no objections I'd like to move pytest-timeout to the pytest-dev team on bitbucket as well. Regards, Floris

Re: [pytest-dev] release checklist / de-monopolizing release process

Hi, If we assume that pytest-2.7.X will be bugfix only we could tie its doc target to latest and ask everybody who does doc enhancements to target their PRs to latest. Seems reasonable to me, but what about doc fixes for features which will be released only on 2.8.0? This means that even

Re: [pytest-dev] how to handle 'parameterize' misspelling

Hi Brianna, Between the two options, I would go for option 2. I don't see much benefit in an alias, as long as an early error warns the user about the mistake. Wasn't there plans to eventually only allow users to use marks previously declared, instead of generating them dynamically while

Re: [pytest-dev] pytest-twisted needs a new maintainer

I'm OK as well. :) On Fri, Mar 6, 2015 at 7:32 PM, Anatoly Bubenkov bubenk...@gmail.com wrote: i vote for adding Christian and Ralf to the pytest-dev and acceping pytest-twisted to the new home! On 6 March 2015 at 23:29, Christian Long christianzlo...@gmail.com wrote: On 3 March 2015 at

[pytest-dev] PyCharm skeletons for pytest

Hi all, I've implemented PyCharm skeletons for pytest. Skeletons are hints to PyCharm's auto-completion engine for modules that make heavy use of dynamic declarations, such as pytest. To install it, type: cd $HOME/.PyCharm40/config git clone https://github.com/nicoddemus/python-skeletons.git -b

Re: [pytest-dev] Running a parametrized test case in multiple CPUs

Have you tried using pytest-xdist? Cheers, On Sat, Dec 6, 2014 at 4:26 PM, Goncalo Morgado goncalo.ma...@gmail.com wrote: Hi pytest community, I am not sure this is the right place to ask this, and I am sorry if it's not. I am trying to make use of multiple CPUs to run my tests, which I

Re: [pytest-dev] Pytest fails with the wrong error when unicode_literals is present

from the frame with the failed assert. Cheers, Bruno On 25 November 2014 at 12:49, Bruno Oliveira nicodde...@gmail.com wrote: Hi everyone, Besides the problem that reinterpret is executing code in a context without unicode_literals enabled, this also showcases that when moving a fixture

Re: [pytest-dev] Pytest fails with the wrong error when unicode_literals is present

Hi everyone, Besides the problem that reinterpret is executing code in a context without unicode_literals enabled, this also showcases that when moving a fixture with has asserts on it from a test file to a conftest file, asserts will not be rewritten anymore and reinterpretation will be used

Re: [pytest-dev] xdist and data sharing during execution in parallel

Hi Ayelet, According to http://codespeak.net/execnet/example/hybridpython.html#dumps-loads-examples, execnet only supports built-in types, so trying to send `node.config.global_data` to the slaves won't work. I'm assuming that `PersistentDict` is similar to `shelve`, so another option would be

Re: [pytest-dev] Disabling timeout for pdb

, On Sun, Sep 14, 2014 at 12:00 PM, holger krekel hol...@merlinux.eu wrote: Hi Wolfgang, Bruno, On Sat, Sep 13, 2014 at 15:53 -0300, Bruno Oliveira wrote: Hi, 1. Am I missing something or does pytest indeed completely seal off its internals? Not really, you can access _pytest module

Re: [pytest-dev] Encouraging the use of bookmarks rather then branches

I stumbled on the same thing. It's unfortunate that Bitbucket's support for bookmarks in PRs is lacking. :( Does any one know if the PR updates automatically when further commits are made, as Florian, asked? I have no problem myself in using bookmarks, but the Contributing section should mention

Re: [pytest-dev] Encouraging the use of bookmarks rather then branches

On Thu, Aug 14, 2014 at 6:52 PM, Floris Bruynooghe f...@devork.be wrote: Yes, that is unfortunate. But note that for a simple contribution, as explained by the CONTRIBUTING.rst guide, this does not even occur since you won't be creating more then one head. So one can simply create the PR

Re: [pytest-dev] extended asserts

Hi, Perhaps this could a plugin (pytest-datadiff)? I know you can customize assertion messages for other types (see http://pytest.org/latest/assert.html#defining-your-own-assertion-comparison), but I don't know how that plays with assertions already built in pytest. Cheers, On Tue, Jul 29,

Re: [pytest-dev] extended asserts

Nice, be sure to keep the mailing list informed. :) Cheers, On Tue, Jul 29, 2014 at 5:17 PM, Anatoly Bubenkov bubenk...@gmail.com wrote: Yes I'll do it as a separate plugin first Then we can think about including it in the core On Jul 29, 2014 9:46 PM, Bruno Oliveira nicodde...@gmail.com

Re: [pytest-dev] `pytest.main()` frozen by cx_freeze

Hi all, For future reference, I created a repository with a solution at https://github.com/nicoddemus/cx_freeze_pytest_example. Cheers, On Sun, Jul 27, 2014 at 12:57 AM, Bruno Oliveira nicodde...@gmail.com wrote: Hi all, I managed to get it to work by explicitly importing pytest and py

Re: [pytest-dev] `pytest.main()` frozen by cx_freeze

it. Also created a PR that eliminates py.std use from pytest, although I could get the frozen executable to work without needing that after all. Just went ahead with the PR because Holger showed interest on it. :) Cheers, On Thu, Jul 24, 2014 at 12:24 PM, Bruno Oliveira nicodde...@gmail.com wrote

Re: [pytest-dev] `pytest.main()` frozen by cx_freeze

Hi Holger, On Thu, Jul 24, 2014 at 11:36 AM, holger krekel hol...@merlinux.eu wrote: i think there are two ways to solve this: - find out how to make py.std work with cx_freeze (haven't looked at that myself yet) I'm investigating this and will share any findings. - eliminate use of

[pytest-dev] `pytest.main()` frozen by cx_freeze

Hi everyone, I'm having trouble getting pytest.main() to run inside a frozen script created by cx_freeze (12-line source code here: https://gist.github.com/nicoddemus/5458ca3fc5241cedaff3); when I run the generated executable (I'm on windows), I get this exception: Traceback (most recent call

Re: [pytest-dev] logo is online

Hi, In my opinion BW would fit better with the rest of the site. Cheers. On Sun, Jun 1, 2014 at 7:09 AM, holger krekel hol...@merlinux.eu wrote: Hi all, i just put the new pytest logo online: http://pytest.org/latest/ Wondering if it's too colorful and we just use the BW version.

Re: [pytest-dev] Changing the behavior of --junitxml

Same here. I think a better approach would be a new flag. Perhaps --append-to-junitxml? On Tue, Jan 21, 2014 at 8:46 PM, Jason R. Coombs jar...@jaraco.com wrote: Surely some depend on the expectation to overwrite. Most of our tests run under Jenkins where the junitxml file is left around to

Re: [pytest-dev] solving the too static fixture scope problem

On Fri, Oct 11, 2013 at 8:14 AM, Vladimir Keleshev vladi...@keleshev.comwrote: If you refer to tmpdir/monkeypatch and potentially others, i agree that the current behaviour is more surprising (sharing the tmpdir across multiple fixtures which don't even neccessarily know about each

Re: [pytest-dev] (new) pytest plugins / note to plugin authors

this to a live app that periodically fetches that information to keep it up to date if you think it is necessary. How does that sound? Cheers, Bruno On Fri, Oct 4, 2013 at 7:18 PM, holger krekel hol...@merlinux.eu wrote: On Fri, Oct 04, 2013 at 18:43 -0300, Bruno Oliveira wrote: But even just collecting

Re: [pytest-dev] (new) pytest plugins / note to plugin authors

Hi Holger, I would be glad to help on that front, if I can. :) Did you give any thoughts on how this could be done? Cheers, On Fri, Oct 4, 2013 at 10:09 AM, holger krekel hol...@merlinux.eu wrote: I just did three pytest plugin releases to get out a few minor fixes and improvements.

<    1   2   3   4   5