From nicoddemus at gmail.com  Thu Sep  1 20:26:27 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 02 Sep 2016 00:26:27 +0000
Subject: [pytest-dev] pytest 3.0.2 released
Message-ID: <CA+RQFfcZcDPzDQSJC9xeChRZQyY85YR-XVsbacLue56g24JmxQ@mail.gmail.com>

Hi everyone,

pytest 3.0.2 has just been released to PyPI.

This release fixes some regressions and bugs reported in version 3.0.1,
being a
drop-in replacement.

To upgrade::

  pip install --upgrade pytest

The changelog is available at http://doc.pytest.org/en/latest/changelog.html
.

Thanks to all who contributed to this release, among them:

* Ahn Ki-Wook
* Bruno Oliveira
* Florian Bruhin
* Jordan Guymon
* Raphael Pierzina
* Ronny Pfannschmidt
* mbyt

Happy testing,
The pytest Development Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160902/f57e21d2/attachment.html>

From zma4580 at gmail.com  Sun Sep  4 16:50:10 2016
From: zma4580 at gmail.com (Zack Allen)
Date: Sun, 4 Sep 2016 16:50:10 -0400
Subject: [pytest-dev] Shipping conftest.py in a python library
Message-ID: <CAMJF5pJiqpo0pk2wHUuHznU89NqvB4_9ABfg8t3zYtatjy5XCg@mail.gmail.com>

Hi all. I have a repo that takes advantage of py.test and ships itself w/
py.test for implementers -> https://github.com/fastly/ftw.

What im having trouble with is that Id like someone to `pip install ftw`
and have the conftest.py under test/conftest.py in my repo available to
them. Is there a way I can ship conftest.py from my github and hav eit be
in the path when people pip install?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160904/9aef1f83/attachment.html>

From rpfannsc at redhat.com  Mon Sep  5 03:05:42 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Mon, 5 Sep 2016 09:05:42 +0200
Subject: [pytest-dev] Shipping conftest.py in a python library
In-Reply-To: <CAMJF5pJiqpo0pk2wHUuHznU89NqvB4_9ABfg8t3zYtatjy5XCg@mail.gmail.com>
References: <CAMJF5pJiqpo0pk2wHUuHznU89NqvB4_9ABfg8t3zYtatjy5XCg@mail.gmail.com>
Message-ID: <CAA10jzNOhH3PCOyk9TPvRZ-SoJZ=j20JKmhRGXUW81yd9Cn+YA@mail.gmail.com>

Hi Zach,

the classical way to do that is to turn what is a conftest into a normal
python package
afterwards any project can put that into the pytest_plugins variable.

also you could add a setuptools entrypoint like the normal 3rd party pytest
plugins use to enable it in all cases

-- Ronny

2016-09-04 22:50 GMT+02:00 Zack Allen <zma4580 at gmail.com>:

> Hi all. I have a repo that takes advantage of py.test and ships itself w/
> py.test for implementers -> https://github.com/fastly/ftw.
>
> What im having trouble with is that Id like someone to `pip install ftw`
> and have the conftest.py under test/conftest.py in my repo available to
> them. Is there a way I can ship conftest.py from my github and hav eit be
> in the path when people pip install?
>
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160905/77903f05/attachment.html>

From flub at devork.be  Mon Sep  5 07:11:12 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Mon, 5 Sep 2016 12:11:12 +0100
Subject: [pytest-dev] [proposal] deprecating the pytest_namespace hook
In-Reply-To: <7dbcc626-05fd-6a29-22a0-6594a65cd195@ronnypfannschmidt.de>
References: <ff0c4605-7ef5-7ad9-9d0b-efeab2261e94@ronnypfannschmidt.de>
 <CA+RQFfeZALPjy0j+-uF5bwZiEfJveNTk6sPVMQKbq-f2ns1e4A@mail.gmail.com>
 <2dadfdf1-c45e-c85e-8b86-cc31e62e8d57@ronnypfannschmidt.de>
 <CA+RQFfeKf_hD__OHKjemK+CFXfXSAwimc6LTrrAx4S7dLSwjyw@mail.gmail.com>
 <7dbcc626-05fd-6a29-22a0-6594a65cd195@ronnypfannschmidt.de>
Message-ID: <20160905111112.oc44lw64bpunocn4@laurie.devork.be>

On Fri, Aug 26, 2016 at 03:06:57PM +0200, Ronny Pfannschmidt wrote:
> On 26.08.2016 15:00, Bruno Oliveira wrote:
> > On Fri, Aug 26, 2016 at 9:54 AM Ronny Pfannschmidt
> > <opensource at ronnypfannschmidt.de
> > <mailto:opensource at ronnypfannschmidt.de>> wrote:
> > 
> >     the problem it creates is, that we need to load plugins before
> >     even parsing the config and before even having config object just
> >     in order to literally monkeypatch a module
> > 
> > You mean that just importing "pytest" you automatically load all
> > plugins? Hmmm I agree that's not very nice.

Yes and no.  I agree it is not nice that hooks get executed on import
time.  But we do need to give plugins the option of extending the
pytest namespace.  So maybe we could introduce a `pytest.init()`
method to explicitly do the execution of hooks (and hence loading of
plugins I guess?).  The `pytest.main()` call could then implicitly
call `pytest.init()` as well, which would be a no-op if it was already
initialised.

> >     the second problem it creates is, it makes the pytest namespace
> >     impossible to introspect for external tools
> > 
> > I agree that's annoying, but that's a problem in general on how dynamic
> > pytest is (IDEs don't autocomplete on fixture parameters either), so I
> > would say this is small.

If the external tools would call `pytest.init()` before introspecting
then it would work just fine.  We could even provide a pylint plugin
by default for this in that case.  That would be nice.


> >     also - import works just fine - there is no need for a dynamic
> >     namespace, people can import from concrete/correct locations
> > 
> > I see, but TBH I don't see how we could just deprecate that without
> > providing an alternative solution which won't break user code. Too many
> > plugins and code depend on that, and we would need to have a **really**
> > good reason to break them all in a future pytest version (I wouldn't
> > even dare to introduce such a deprecation until 4.0 for example).

I'm afraid I agree with Bruno here, I'd even go further and suggest we
can never remove the pytest_namespace hook.  It is just used too
widely by plugins and afaik the documentation even actively
encourages the use.  What I think we could do is clean up the order of
when the hook gets called as I vaguely suggest with the
`pytest.init()` proposal above (note that I haven't fully thought this
through yet).  This would still have to go through some deprecation
cycle obviously as I'm sure there will be some cases that will break,
but at least we'll be providing plugin authors with a clear way they
can make sure to not rely on the current funky ordering without
breaking their own public API.


Regards,
Floris

From me at the-compiler.org  Mon Sep  5 07:47:06 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Mon, 5 Sep 2016 13:47:06 +0200
Subject: [pytest-dev] [proposal] deprecating the pytest_namespace hook
In-Reply-To: <20160905111112.oc44lw64bpunocn4@laurie.devork.be>
References: <ff0c4605-7ef5-7ad9-9d0b-efeab2261e94@ronnypfannschmidt.de>
 <CA+RQFfeZALPjy0j+-uF5bwZiEfJveNTk6sPVMQKbq-f2ns1e4A@mail.gmail.com>
 <2dadfdf1-c45e-c85e-8b86-cc31e62e8d57@ronnypfannschmidt.de>
 <CA+RQFfeKf_hD__OHKjemK+CFXfXSAwimc6LTrrAx4S7dLSwjyw@mail.gmail.com>
 <7dbcc626-05fd-6a29-22a0-6594a65cd195@ronnypfannschmidt.de>
 <20160905111112.oc44lw64bpunocn4@laurie.devork.be>
Message-ID: <20160905114706.rraoj3nvdalaj2iu@tonks>

* Floris Bruynooghe <flub at devork.be> [2016-09-05 12:11:12 +0100]:
> > >     the second problem it creates is, it makes the pytest namespace
> > >     impossible to introspect for external tools
> > > 
> > > I agree that's annoying, but that's a problem in general on how dynamic
> > > pytest is (IDEs don't autocomplete on fixture parameters either), so I
> > > would say this is small.
> 
> If the external tools would call `pytest.init()` before introspecting
> then it would work just fine.  We could even provide a pylint plugin
> by default for this in that case.  That would be nice.

FWIW I recently updated pylint's "brain" module for pytest so it at
least understands stuff added in pytest 3:

https://github.com/PyCQA/astroid/commit/8ec025fa36c9c627bcdd6da7fab56271731d47eb

But I agree this is less than optimal.

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160905/c748f04c/attachment.sig>

From zma4580 at gmail.com  Mon Sep  5 12:40:59 2016
From: zma4580 at gmail.com (Zack Allen)
Date: Mon, 5 Sep 2016 12:40:59 -0400
Subject: [pytest-dev] Shipping conftest.py in a python library
In-Reply-To: <CAA10jzNOhH3PCOyk9TPvRZ-SoJZ=j20JKmhRGXUW81yd9Cn+YA@mail.gmail.com>
References: <CAMJF5pJiqpo0pk2wHUuHznU89NqvB4_9ABfg8t3zYtatjy5XCg@mail.gmail.com>
 <CAA10jzNOhH3PCOyk9TPvRZ-SoJZ=j20JKmhRGXUW81yd9Cn+YA@mail.gmail.com>
Message-ID: <CAMJF5pJwEfaH_0XhE8wFedVe1+3c6iDhiuOj4NdVBH+VWWvFTw@mail.gmail.com>

Great! Thank you!

On Mon, Sep 5, 2016 at 3:05 AM, Ronny Pfannschmidt <rpfannsc at redhat.com>
wrote:

> Hi Zach,
>
> the classical way to do that is to turn what is a conftest into a normal
> python package
> afterwards any project can put that into the pytest_plugins variable.
>
> also you could add a setuptools entrypoint like the normal 3rd party
> pytest plugins use to enable it in all cases
>
> -- Ronny
>
> 2016-09-04 22:50 GMT+02:00 Zack Allen <zma4580 at gmail.com>:
>
>> Hi all. I have a repo that takes advantage of py.test and ships itself w/
>> py.test for implementers -> https://github.com/fastly/ftw.
>>
>> What im having trouble with is that Id like someone to `pip install ftw`
>> and have the conftest.py under test/conftest.py in my repo available to
>> them. Is there a way I can ship conftest.py from my github and hav eit be
>> in the path when people pip install?
>>
>> _______________________________________________
>> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160905/9d70d35f/attachment.html>

From rpfannsc at redhat.com  Wed Sep  7 07:33:05 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Wed, 7 Sep 2016 13:33:05 +0200
Subject: [pytest-dev] [proposal] regendoc automation via travis + pytest-bot
 on GH
Message-ID: <CAA10jzPHrg12fXhWwEkMB9wbQVWZ1v_ixDkPKmP3SoVgM+s3dQ@mail.gmail.com>

hi,

i would like to propose an regendoc automation using the pytest-bot

the basic idea is, to have travis deploys on master/features that would run
regendoc, commit changes as pytest-bot, upload those to
pytest-bot/pytest-dev and open pull requests against pytest itself

all we would need for that is a github api token fir pushes and creating
pull request objects

the bot user would be both - a perfect place to put the intermediate
commits and as originator for the automated pull requests coming from travis


-- Ronny
-- 

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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160907/bf21065d/attachment.html>

From rpfannsc at redhat.com  Wed Sep  7 05:38:54 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Wed, 7 Sep 2016 11:38:54 +0200
Subject: [pytest-dev] Proposal: python namespacign for markings/marker
 objects
Message-ID: <CAA10jzPD=-PeXNYK5zoB58KdAPGGixg28t78wUFVCE5NMKQ=Xw@mail.gmail.com>

Hi all,

while trying to turn various internal markers of a work project
into public plugins, i noticed a very plain problems - different other
plugins used the same generic marker name for different purposes/intents

such a flat namespace really doesn't scale

as such i would like to propose having marker types and objects as
importable objects


for example



import pytest
from pytest_bugzilla import Blocker


@pytest.mark(Blocker(123))
def test_fun():
  pass

that way we can do both, reuse python name-spacing *and* use more
meaningful objects for markings

-- Ronny

-- 

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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160907/29fc63e1/attachment.html>

From rpfannsc at redhat.com  Wed Sep  7 09:39:34 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Wed, 7 Sep 2016 15:39:34 +0200
Subject: [pytest-dev] [wishlist] handling reuse of pytest plugins outside of
 pytest
Message-ID: <CAA10jzNmBKi1ZrmV+TasYCro64SR500N1R9xMxhGHUYfvBSqGA@mail.gmail.com>

Hi,

recently i am starting to very painfully hit a massive wall
which is trying to use pytest integrated functionality outside of a test run

the inability to use them in some way is pretty much actively holding me
back
from running test helpers in ipython sessions & co

at work we work around that by the means of having global instead of using
fixtures
and by re-implementing functionality and the using it both in fixtures and
in

however we would like to get rid of that in some way

but with the current constraints of being unable to use anything outside of
a test run we are pretty much forced to keep own implementations of plugins
like
pytest-baseurl. pytest-selenium, pytest-variables and more


-- Ronny

-- 

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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160907/4150dadf/attachment.html>

From nicoddemus at gmail.com  Wed Sep  7 11:03:18 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 07 Sep 2016 15:03:18 +0000
Subject: [pytest-dev] [proposal] regendoc automation via travis +
 pytest-bot on GH
In-Reply-To: <CAA10jzPHrg12fXhWwEkMB9wbQVWZ1v_ixDkPKmP3SoVgM+s3dQ@mail.gmail.com>
References: <CAA10jzPHrg12fXhWwEkMB9wbQVWZ1v_ixDkPKmP3SoVgM+s3dQ@mail.gmail.com>
Message-ID: <CA+RQFfc8iAWDd9f7JdTxyfXAcG2xU8VYD7n5T_mhkKMBb9cRRQ@mail.gmail.com>

Hi Ronny,

To me it sounds great if we could automate regendoc. As we discussed
online, the approach you propose sounds good as well. Are you planning to
tackle this anytime soon?

Cheers,
Bruno

On Wed, Sep 7, 2016 at 8:33 AM Ronny Pfannschmidt <rpfannsc at redhat.com>
wrote:

> hi,
>
> i would like to propose an regendoc automation using the pytest-bot
>
> the basic idea is, to have travis deploys on master/features that would
> run regendoc, commit changes as pytest-bot, upload those to
> pytest-bot/pytest-dev and open pull requests against pytest itself
>
> all we would need for that is a github api token fir pushes and creating
> pull request objects
>
> the bot user would be both - a perfect place to put the intermediate
> commits and as originator for the automated pull requests coming from travis
>
>
> -- Ronny
> --
>
> 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
>
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160907/6b3798b7/attachment.html>

From rpfannsc at redhat.com  Wed Sep  7 11:05:18 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Wed, 7 Sep 2016 17:05:18 +0200
Subject: [pytest-dev] [proposal] regendoc automation via travis +
 pytest-bot on GH
In-Reply-To: <CA+RQFfc8iAWDd9f7JdTxyfXAcG2xU8VYD7n5T_mhkKMBb9cRRQ@mail.gmail.com>
References: <CAA10jzPHrg12fXhWwEkMB9wbQVWZ1v_ixDkPKmP3SoVgM+s3dQ@mail.gmail.com>
 <CA+RQFfc8iAWDd9f7JdTxyfXAcG2xU8VYD7n5T_mhkKMBb9cRRQ@mail.gmail.com>
Message-ID: <CAA10jzNL3vW5nafjtCA4e5KtgSoYkdFHEEzGAg_yx9R4XeSnxQ@mail.gmail.com>

Hi Bruno,

i hope i can make a initial take at the weekend,
i might need some support wrt api tokens/credentials

2016-09-07 17:03 GMT+02:00 Bruno Oliveira <nicoddemus at gmail.com>:

> Hi Ronny,
>
> To me it sounds great if we could automate regendoc. As we discussed
> online, the approach you propose sounds good as well. Are you planning to
> tackle this anytime soon?
>
> Cheers,
> Bruno
>
> On Wed, Sep 7, 2016 at 8:33 AM Ronny Pfannschmidt <rpfannsc at redhat.com>
> wrote:
>
>> hi,
>>
>> i would like to propose an regendoc automation using the pytest-bot
>>
>> the basic idea is, to have travis deploys on master/features that would
>> run regendoc, commit changes as pytest-bot, upload those to
>> pytest-bot/pytest-dev and open pull requests against pytest itself
>>
>> all we would need for that is a github api token fir pushes and creating
>> pull request objects
>>
>> the bot user would be both - a perfect place to put the intermediate
>> commits and as originator for the automated pull requests coming from travis
>>
>>
>> -- Ronny
>> --
>>
>> 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
>>
>> _______________________________________________
>> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160907/31363ce8/attachment-0001.html>

From nicoddemus at gmail.com  Wed Sep  7 11:11:36 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 07 Sep 2016 15:11:36 +0000
Subject: [pytest-dev] [proposal] regendoc automation via travis +
 pytest-bot on GH
In-Reply-To: <CAA10jzNL3vW5nafjtCA4e5KtgSoYkdFHEEzGAg_yx9R4XeSnxQ@mail.gmail.com>
References: <CAA10jzPHrg12fXhWwEkMB9wbQVWZ1v_ixDkPKmP3SoVgM+s3dQ@mail.gmail.com>
 <CA+RQFfc8iAWDd9f7JdTxyfXAcG2xU8VYD7n5T_mhkKMBb9cRRQ@mail.gmail.com>
 <CAA10jzNL3vW5nafjtCA4e5KtgSoYkdFHEEzGAg_yx9R4XeSnxQ@mail.gmail.com>
Message-ID: <CA+RQFfcxPPznmrEGVQsot6PS8NRRuADCS3TcRQv0n=MnENi2bA@mail.gmail.com>

Really? Well, feel free to send me a ping, although I'm pretty sure you
have the same credentials as me. :)

Cheers,
Bruno.

On Wed, Sep 7, 2016 at 12:05 PM Ronny Pfannschmidt <rpfannsc at redhat.com>
wrote:

> Hi Bruno,
>
> i hope i can make a initial take at the weekend,
> i might need some support wrt api tokens/credentials
>
> 2016-09-07 17:03 GMT+02:00 Bruno Oliveira <nicoddemus at gmail.com>:
>
>> Hi Ronny,
>>
>> To me it sounds great if we could automate regendoc. As we discussed
>> online, the approach you propose sounds good as well. Are you planning to
>> tackle this anytime soon?
>>
>> Cheers,
>> Bruno
>>
>> On Wed, Sep 7, 2016 at 8:33 AM Ronny Pfannschmidt <rpfannsc at redhat.com>
>> wrote:
>>
>>> hi,
>>>
>>> i would like to propose an regendoc automation using the pytest-bot
>>>
>>> the basic idea is, to have travis deploys on master/features that would
>>> run regendoc, commit changes as pytest-bot, upload those to
>>> pytest-bot/pytest-dev and open pull requests against pytest itself
>>>
>>> all we would need for that is a github api token fir pushes and creating
>>> pull request objects
>>>
>>> the bot user would be both - a perfect place to put the intermediate
>>> commits and as originator for the automated pull requests coming from travis
>>>
>>>
>>> -- Ronny
>>> --
>>>
>>> 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
>>>
>>> _______________________________________________
>>> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160907/0bbf0dfe/attachment.html>

From nicoddemus at gmail.com  Wed Sep  7 15:22:20 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 07 Sep 2016 19:22:20 +0000
Subject: [pytest-dev] [wishlist] handling reuse of pytest plugins
 outside of pytest
In-Reply-To: <CAA10jzNmBKi1ZrmV+TasYCro64SR500N1R9xMxhGHUYfvBSqGA@mail.gmail.com>
References: <CAA10jzNmBKi1ZrmV+TasYCro64SR500N1R9xMxhGHUYfvBSqGA@mail.gmail.com>
Message-ID: <CA+RQFfccNr01-EHfDwQ2k60eaqra=_CrwM_AaWDyeqksY3RMyw@mail.gmail.com>

Hey Ronny,

Can you provide some examples of what you would like to accomplish? At
least to me your email is a little vague and I wouldn't know where to start
discussion about it...

On Wed, Sep 7, 2016 at 10:47 AM Ronny Pfannschmidt <rpfannsc at redhat.com>
wrote:

> Hi,
>
> recently i am starting to very painfully hit a massive wall
> which is trying to use pytest integrated functionality outside of a test
> run
>
> the inability to use them in some way is pretty much actively holding me
> back
> from running test helpers in ipython sessions & co
>
> at work we work around that by the means of having global instead of using
> fixtures
> and by re-implementing functionality and the using it both in fixtures and
> in
>
> however we would like to get rid of that in some way
>
> but with the current constraints of being unable to use anything outside
> of a test run we are pretty much forced to keep own implementations of
> plugins like
> pytest-baseurl. pytest-selenium, pytest-variables and more
>
>
> -- Ronny
>
> --
>
> 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
>
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160907/4da8b265/attachment.html>

From rpfannsc at redhat.com  Thu Sep  8 02:00:13 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Thu, 8 Sep 2016 08:00:13 +0200
Subject: [pytest-dev] [wishlist] handling reuse of pytest plugins
 outside of pytest
In-Reply-To: <CA+RQFfccNr01-EHfDwQ2k60eaqra=_CrwM_AaWDyeqksY3RMyw@mail.gmail.com>
References: <CAA10jzNmBKi1ZrmV+TasYCro64SR500N1R9xMxhGHUYfvBSqGA@mail.gmail.com>
 <CA+RQFfccNr01-EHfDwQ2k60eaqra=_CrwM_AaWDyeqksY3RMyw@mail.gmail.com>
Message-ID: <CAA10jzNo+RxuGH7Vx50_807M+1E1OoNA3=hsM3rMYj-qQjdB2Q@mail.gmail.com>

agin after accidential off-list:

A simple non code example would be using fixtures based on pytest-selenium
in a ipython session without running a test

2016-09-07 21:22 GMT+02:00 Bruno Oliveira <nicoddemus at gmail.com>:

> Hey Ronny,
>
> Can you provide some examples of what you would like to accomplish? At
> least to me your email is a little vague and I wouldn't know where to start
> discussion about it...
>
> On Wed, Sep 7, 2016 at 10:47 AM Ronny Pfannschmidt <rpfannsc at redhat.com>
> wrote:
>
>> Hi,
>>
>> recently i am starting to very painfully hit a massive wall
>> which is trying to use pytest integrated functionality outside of a test
>> run
>>
>> the inability to use them in some way is pretty much actively holding me
>> back
>> from running test helpers in ipython sessions & co
>>
>> at work we work around that by the means of having global instead of
>> using fixtures
>> and by re-implementing functionality and the using it both in fixtures
>> and in
>>
>> however we would like to get rid of that in some way
>>
>> but with the current constraints of being unable to use anything outside
>> of a test run we are pretty much forced to keep own implementations of
>> plugins like
>> pytest-baseurl. pytest-selenium, pytest-variables and more
>>
>>
>> -- Ronny
>>
>> --
>>
>> 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
>>
>> _______________________________________________
>> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160908/b76f222c/attachment.html>

From rpfannsc at redhat.com  Thu Sep  8 07:51:30 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Thu, 8 Sep 2016 13:51:30 +0200
Subject: [pytest-dev] on progressing to fix up marks
Message-ID: <CAA10jzMaJRa8-FXEVQfcmtZY7msKkODNV_n_EXK3OQr1D9Oc0A@mail.gmail.com>

hi everyone

i began seeing a path towards cleaning up marks without breaking everything

i started with https://github.com/pytest-dev/pytest/pull/1921
which introduces a correct mechanism for using marked values in parameter
sets

and https://github.com/pytest-dev/pytest/pull/1923
which introduces an actual representation for single marks (before marks
existed only as decorators or mashed into a markinfo (which is a mark and a
list of marks)

after following up with those pull requests, i want to break some apis that
introduce bugs and mistakes

the first part of that is putting lists of self-owned mark objects onto
collection nodes (and only the mark objects) and viewing the markers of a
test node as the union of those owned markers

at the same pace i would completely deprecate the named mark objects that
are smeared onto functions, so we can remove them for pytest 4.0 or 5.0

i would also leave the breaking behaviour of those markinfo objects intact
the canonical source for a union view of the marks should always be the
test item, not the function object being marked

node.get_marker and node.add_marker will need to get "broken" as well
currently add_marker replaces instead of adding a additional mark

parameterization also does not consider the possibility of more than one
mark of the same value and just puts them into a dict by name (thus
discarding values)
while fixing that i want to discard the broken mechanism of nesting marks
in order to try and expose marking for values (xfail(myvalue) instead of
marked(myvalue, xfail) is just a mess)

the real problem area i see is the really strange and pretty much
incomprehensible mix of keywords, marks, extra-keywords and the various
matcher objects involved in that

i'm not confident at all this mess can be de-tangled without regressions or
planned compatibility breaks,

as such i'd rather plan compatibility breakage than running into regressions

-- Ronny



-- 

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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160908/9d0bb3c1/attachment.html>

From holger at merlinux.eu  Mon Sep 12 04:57:07 2016
From: holger at merlinux.eu (holger krekel)
Date: Mon, 12 Sep 2016 10:57:07 +0200
Subject: [pytest-dev] pluggy moved to pytest-dev
Message-ID: <20160912085707.GB24513@uwanda>


Ronny asked me to move the pluggy (pluginmanager used by pytest, devpi, tox, others) repo to pytest-dev organisation and i just did it.  It's now at:

    https://github.com/pytest-dev/pluggy

Also added the same people to the pluggy pypi page who can release pytest.

cheers,
holger

From nicoddemus at gmail.com  Mon Sep 12 19:11:30 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 12 Sep 2016 23:11:30 +0000
Subject: [pytest-dev] pluggy moved to pytest-dev
In-Reply-To: <20160912085707.GB24513@uwanda>
References: <20160912085707.GB24513@uwanda>
Message-ID: <CA+RQFfcdgoxNCSF_6qBK7vx-P0+6KQP5F6uevx6REP6HFUdXSA@mail.gmail.com>

Nice!

Holger, is it OK with you if someone with push access to PyPI publish 0.4
soonish? This is required by
https://github.com/pytest-dev/pytest/issues/1637

Cheers,
Bruno.

On Mon, Sep 12, 2016 at 5:59 AM holger krekel <holger at merlinux.eu> wrote:

>
> Ronny asked me to move the pluggy (pluginmanager used by pytest, devpi,
> tox, others) repo to pytest-dev organisation and i just did it.  It's now
> at:
>
>     https://github.com/pytest-dev/pluggy
>
> Also added the same people to the pluggy pypi page who can release pytest.
>
> cheers,
> holger
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160912/a0248f00/attachment.html>

From vital.kudzelka at gmail.com  Tue Sep 13 02:34:57 2016
From: vital.kudzelka at gmail.com (Vital Kudzelka)
Date: Tue, 13 Sep 2016 06:34:57 +0000
Subject: [pytest-dev] Move pytest-flask plugin to pytest-dev
Message-ID: <CAKsDsKXpDC2roTmo98hM5iUmg8jGCUJv-Mf8NnzZRXLvBr8Jig@mail.gmail.com>

Hi,

I would to like to know if there are any objections to move the pytest-flask
plugins to pytest-dev organization.

Plugin are in PyPI, have an appropriate README, license, continuous
integration and documentation:
https://github.com/vitalk/pytest-flask
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160913/ef8f45e7/attachment.html>

From opensource at ronnypfannschmidt.de  Tue Sep 13 03:39:36 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Tue, 13 Sep 2016 09:39:36 +0200
Subject: [pytest-dev] Move pytest-flask plugin to pytest-dev
In-Reply-To: <CAKsDsKXpDC2roTmo98hM5iUmg8jGCUJv-Mf8NnzZRXLvBr8Jig@mail.gmail.com>
References: <CAKsDsKXpDC2roTmo98hM5iUmg8jGCUJv-Mf8NnzZRXLvBr8Jig@mail.gmail.com>
Message-ID: <7afa55ec-41fa-de8f-ab48-752c39dbfea1@ronnypfannschmidt.de>

Hi Vital

at first glance there nothing stopping,

but since the plugin is framework specific,
i also wonder, if it perhaps would have a good place under the pallets org
(which has the flask ecosystem)

-- Ronny

From holger at merlinux.eu  Tue Sep 13 05:58:25 2016
From: holger at merlinux.eu (holger krekel)
Date: Tue, 13 Sep 2016 11:58:25 +0200
Subject: [pytest-dev] pluggy moved to pytest-dev
In-Reply-To: <CA+RQFfcdgoxNCSF_6qBK7vx-P0+6KQP5F6uevx6REP6HFUdXSA@mail.gmail.com>
References: <20160912085707.GB24513@uwanda>
 <CA+RQFfcdgoxNCSF_6qBK7vx-P0+6KQP5F6uevx6REP6HFUdXSA@mail.gmail.com>
Message-ID: <20160913095825.GI26884@uwanda>

On Mon, Sep 12, 2016 at 23:11 +0000, Bruno Oliveira wrote:
> Nice!
> 
> Holger, is it OK with you if someone with push access to PyPI publish 0.4
> soonish? This is required by
> https://github.com/pytest-dev/pytest/issues/1637

fine with me.

holger

> Cheers,
> Bruno.
> 
> On Mon, Sep 12, 2016 at 5:59 AM holger krekel <holger at merlinux.eu> wrote:
> 
> >
> > Ronny asked me to move the pluggy (pluginmanager used by pytest, devpi,
> > tox, others) repo to pytest-dev organisation and i just did it.  It's now
> > at:
> >
> >     https://github.com/pytest-dev/pluggy
> >
> > Also added the same people to the pluggy pypi page who can release pytest.
> >
> > cheers,
> > holger
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >

From nicoddemus at gmail.com  Tue Sep 13 12:26:41 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 13 Sep 2016 16:26:41 +0000
Subject: [pytest-dev] Move pytest-flask plugin to pytest-dev
In-Reply-To: <7afa55ec-41fa-de8f-ab48-752c39dbfea1@ronnypfannschmidt.de>
References: <CAKsDsKXpDC2roTmo98hM5iUmg8jGCUJv-Mf8NnzZRXLvBr8Jig@mail.gmail.com>
 <7afa55ec-41fa-de8f-ab48-752c39dbfea1@ronnypfannschmidt.de>
Message-ID: <CA+RQFfeS2vGm9qqwdnLFAgdix-MMYp5PFPRGqNsoSJn9RQsfdA@mail.gmail.com>

Hi,

I'm certainly fine with it as well. Let's just wait for Vital to answer to
Ronny's suggestion before moving forward.

Cheers,

On Tue, Sep 13, 2016 at 4:39 AM Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

> Hi Vital
>
> at first glance there nothing stopping,
>
> but since the plugin is framework specific,
> i also wonder, if it perhaps would have a good place under the pallets org
> (which has the flask ecosystem)
>
> -- 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160913/cb5769b4/attachment.html>

From vital.kudzelka at gmail.com  Tue Sep 13 12:48:50 2016
From: vital.kudzelka at gmail.com (Vital Kudzelka)
Date: Tue, 13 Sep 2016 16:48:50 +0000
Subject: [pytest-dev] Move pytest-flask plugin to pytest-dev
In-Reply-To: <CA+RQFfeS2vGm9qqwdnLFAgdix-MMYp5PFPRGqNsoSJn9RQsfdA@mail.gmail.com>
References: <CAKsDsKXpDC2roTmo98hM5iUmg8jGCUJv-Mf8NnzZRXLvBr8Jig@mail.gmail.com>
 <7afa55ec-41fa-de8f-ab48-752c39dbfea1@ronnypfannschmidt.de>
 <CA+RQFfeS2vGm9qqwdnLFAgdix-MMYp5PFPRGqNsoSJn9RQsfdA@mail.gmail.com>
Message-ID: <CAKsDsKVhFmH3YCSkj+u7_PrFdNRKZ=oWqpJovBfJvFahK5OV8Q@mail.gmail.com>

I prefer to keep plugin under pytest-dev for consistency with pytest-django.

On Tue, Sep 13, 2016 at 7:26 PM Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Hi,
>
> I'm certainly fine with it as well. Let's just wait for Vital to answer to
> Ronny's suggestion before moving forward.
>
> Cheers,
>
> On Tue, Sep 13, 2016 at 4:39 AM Ronny Pfannschmidt <
> opensource at ronnypfannschmidt.de> wrote:
>
>> Hi Vital
>>
>> at first glance there nothing stopping,
>>
>> but since the plugin is framework specific,
>> i also wonder, if it perhaps would have a good place under the pallets org
>> (which has the flask ecosystem)
>>
>> -- 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160913/e680cc4c/attachment.html>

From opensource at ronnypfannschmidt.de  Tue Sep 13 16:19:08 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Tue, 13 Sep 2016 22:19:08 +0200
Subject: [pytest-dev] pylib conversation for review and bb ux mistake
Message-ID: <ad89eaf1-5ff1-baf9-c0d9-0197f5f72ae1@ronnypfannschmidt.de>

Hi all,

i prepared pylib for a move to github

the result can be reviewed under
https://github.com/RonnyPfannschmidt-migration-tests/pylib

while preping pylib for the move i declined a few simple pull requests
that where lacking some finishing touches

without realizing that on bitbucket, a decline is final :/

since its my fault i also volunteer for importing and finishing those.

-- Ronny



From nicoddemus at gmail.com  Wed Sep 14 07:13:39 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 14 Sep 2016 11:13:39 +0000
Subject: [pytest-dev] Move pytest-flask plugin to pytest-dev
In-Reply-To: <CAKsDsKVhFmH3YCSkj+u7_PrFdNRKZ=oWqpJovBfJvFahK5OV8Q@mail.gmail.com>
References: <CAKsDsKXpDC2roTmo98hM5iUmg8jGCUJv-Mf8NnzZRXLvBr8Jig@mail.gmail.com>
 <7afa55ec-41fa-de8f-ab48-752c39dbfea1@ronnypfannschmidt.de>
 <CA+RQFfeS2vGm9qqwdnLFAgdix-MMYp5PFPRGqNsoSJn9RQsfdA@mail.gmail.com>
 <CAKsDsKVhFmH3YCSkj+u7_PrFdNRKZ=oWqpJovBfJvFahK5OV8Q@mail.gmail.com>
Message-ID: <CA+RQFfeJOsp93xjMpATva1WjQRabdwJvaV0CexshiF4Xr4A4kA@mail.gmail.com>

Vital,

The steps are detailed here:

https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev

I already created the teams, feel free to transfer ownership of the
repository to me.

Cheers

On Tue, Sep 13, 2016 at 1:49 PM Vital Kudzelka <vital.kudzelka at gmail.com>
wrote:

> I prefer to keep plugin under pytest-dev for consistency with
> pytest-django.
>
> On Tue, Sep 13, 2016 at 7:26 PM Bruno Oliveira <nicoddemus at gmail.com>
> wrote:
>
>> Hi,
>>
>> I'm certainly fine with it as well. Let's just wait for Vital to answer
>> to Ronny's suggestion before moving forward.
>>
>> Cheers,
>>
>> On Tue, Sep 13, 2016 at 4:39 AM Ronny Pfannschmidt <
>> opensource at ronnypfannschmidt.de> wrote:
>>
>>> Hi Vital
>>>
>>> at first glance there nothing stopping,
>>>
>>> but since the plugin is framework specific,
>>> i also wonder, if it perhaps would have a good place under the pallets
>>> org
>>> (which has the flask ecosystem)
>>>
>>> -- 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/781c8e1b/attachment.html>

From nicoddemus at gmail.com  Wed Sep 14 07:56:19 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 14 Sep 2016 11:56:19 +0000
Subject: [pytest-dev] Move pytest-flask plugin to pytest-dev
In-Reply-To: <CA+RQFfeJOsp93xjMpATva1WjQRabdwJvaV0CexshiF4Xr4A4kA@mail.gmail.com>
References: <CAKsDsKXpDC2roTmo98hM5iUmg8jGCUJv-Mf8NnzZRXLvBr8Jig@mail.gmail.com>
 <7afa55ec-41fa-de8f-ab48-752c39dbfea1@ronnypfannschmidt.de>
 <CA+RQFfeS2vGm9qqwdnLFAgdix-MMYp5PFPRGqNsoSJn9RQsfdA@mail.gmail.com>
 <CAKsDsKVhFmH3YCSkj+u7_PrFdNRKZ=oWqpJovBfJvFahK5OV8Q@mail.gmail.com>
 <CA+RQFfeJOsp93xjMpATva1WjQRabdwJvaV0CexshiF4Xr4A4kA@mail.gmail.com>
Message-ID: <CA+RQFffqru=ZEa2m=2nzcZCUBprjvNDFZ0eDf-0R-JfekG8SMQ@mail.gmail.com>

I think the move is complete, let me know if you have any problems.

Cheers,

On Wed, Sep 14, 2016 at 8:13 AM Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Vital,
>
> The steps are detailed here:
>
>
> https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev
>
> I already created the teams, feel free to transfer ownership of the
> repository to me.
>
> Cheers
>
> On Tue, Sep 13, 2016 at 1:49 PM Vital Kudzelka <vital.kudzelka at gmail.com>
> wrote:
>
>> I prefer to keep plugin under pytest-dev for consistency with
>> pytest-django.
>>
>> On Tue, Sep 13, 2016 at 7:26 PM Bruno Oliveira <nicoddemus at gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I'm certainly fine with it as well. Let's just wait for Vital to answer
>>> to Ronny's suggestion before moving forward.
>>>
>>> Cheers,
>>>
>>> On Tue, Sep 13, 2016 at 4:39 AM Ronny Pfannschmidt <
>>> opensource at ronnypfannschmidt.de> wrote:
>>>
>>>> Hi Vital
>>>>
>>>> at first glance there nothing stopping,
>>>>
>>>> but since the plugin is framework specific,
>>>> i also wonder, if it perhaps would have a good place under the pallets
>>>> org
>>>> (which has the flask ecosystem)
>>>>
>>>> -- 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/4b733105/attachment-0001.html>

From holger at merlinux.eu  Wed Sep 14 07:58:18 2016
From: holger at merlinux.eu (holger krekel)
Date: Wed, 14 Sep 2016 13:58:18 +0200
Subject: [pytest-dev] transfer repo / pypi access / ML announce
Message-ID: <20160914115818.GY26884@uwanda>

I am a bit concerned that people who transfer repos to pytest-dev think that it receives magic maintenance because this relevant section in the docs 

http://doc.pytest.org/en/latest/contributing.html#submitting-plugins-to-pytest-dev

is not very explicit about it, even says "sharing some of the maintenance responsibility".  I suggest we explicitely say that maintainers are generally expected to continue maintaining their plugins.

And how about having a "pytest-dev" user which has release rights on pypi for all pytest-dev plugins?  The credentials could be shared in a file in our public repo, encrypted to known GPG public keys. Speaking of which, we could collect gpg keys of contributors in another file.

lastly, if we had a pure pytest-announce mailing list we could announce new pytest-dev plugins (from time to time) and releases there. We can certainly get that list on python.org.

best,
holger

-------------- next part --------------
A non-text attachment was scrubbed...
Name: holger.key
Type: application/pgp-keys
Size: 5607 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/71894e16/attachment.key>

From opensource at ronnypfannschmidt.de  Wed Sep 14 08:01:32 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Wed, 14 Sep 2016 14:01:32 +0200
Subject: [pytest-dev] transfer repo / pypi access / ML announce
In-Reply-To: <20160914115818.GY26884@uwanda>
References: <20160914115818.GY26884@uwanda>
Message-ID: <7b71e741-66ff-1ce2-7f17-cc90d0e1f04f@ronnypfannschmidt.de>

sounds good to me,

can we up the release automation requirements,
so git tag + travis deploys can be used for releasing?

best, Ronny

On 14.09.2016 13:58, holger krekel wrote:
> I am a bit concerned that people who transfer repos to pytest-dev think that it receives magic maintenance because this relevant section in the docs 
>
> http://doc.pytest.org/en/latest/contributing.html#submitting-plugins-to-pytest-dev
>
> is not very explicit about it, even says "sharing some of the maintenance responsibility".  I suggest we explicitely say that maintainers are generally expected to continue maintaining their plugins.
>
> And how about having a "pytest-dev" user which has release rights on pypi for all pytest-dev plugins?  The credentials could be shared in a file in our public repo, encrypted to known GPG public keys. Speaking of which, we could collect gpg keys of contributors in another file.
>
> lastly, if we had a pure pytest-announce mailing list we could announce new pytest-dev plugins (from time to time) and releases there. We can certainly get that list on python.org.
>
> best,
> holger
>
>
>
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/83900329/attachment.html>

From vital.kudzelka at gmail.com  Wed Sep 14 08:09:09 2016
From: vital.kudzelka at gmail.com (Vital Kudzelka)
Date: Wed, 14 Sep 2016 12:09:09 +0000
Subject: [pytest-dev] Move pytest-flask plugin to pytest-dev
In-Reply-To: <CA+RQFffqru=ZEa2m=2nzcZCUBprjvNDFZ0eDf-0R-JfekG8SMQ@mail.gmail.com>
References: <CAKsDsKXpDC2roTmo98hM5iUmg8jGCUJv-Mf8NnzZRXLvBr8Jig@mail.gmail.com>
 <7afa55ec-41fa-de8f-ab48-752c39dbfea1@ronnypfannschmidt.de>
 <CA+RQFfeS2vGm9qqwdnLFAgdix-MMYp5PFPRGqNsoSJn9RQsfdA@mail.gmail.com>
 <CAKsDsKVhFmH3YCSkj+u7_PrFdNRKZ=oWqpJovBfJvFahK5OV8Q@mail.gmail.com>
 <CA+RQFfeJOsp93xjMpATva1WjQRabdwJvaV0CexshiF4Xr4A4kA@mail.gmail.com>
 <CA+RQFffqru=ZEa2m=2nzcZCUBprjvNDFZ0eDf-0R-JfekG8SMQ@mail.gmail.com>
Message-ID: <CAKsDsKX1dTds=dk_iXwVM1EdsSbf6RB9mucJHaF3jdTNqk6iFw@mail.gmail.com>

Ok.

On Wed, Sep 14, 2016 at 2:56 PM Bruno Oliveira <nicoddemus at gmail.com> wrote:

> I think the move is complete, let me know if you have any problems.
>
> Cheers,
>
> On Wed, Sep 14, 2016 at 8:13 AM Bruno Oliveira <nicoddemus at gmail.com>
> wrote:
>
>> Vital,
>>
>> The steps are detailed here:
>>
>>
>> https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev
>>
>> I already created the teams, feel free to transfer ownership of the
>> repository to me.
>>
>> Cheers
>>
>> On Tue, Sep 13, 2016 at 1:49 PM Vital Kudzelka <vital.kudzelka at gmail.com>
>> wrote:
>>
>>> I prefer to keep plugin under pytest-dev for consistency with
>>> pytest-django.
>>>
>>> On Tue, Sep 13, 2016 at 7:26 PM Bruno Oliveira <nicoddemus at gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm certainly fine with it as well. Let's just wait for Vital to answer
>>>> to Ronny's suggestion before moving forward.
>>>>
>>>> Cheers,
>>>>
>>>> On Tue, Sep 13, 2016 at 4:39 AM Ronny Pfannschmidt <
>>>> opensource at ronnypfannschmidt.de> wrote:
>>>>
>>>>> Hi Vital
>>>>>
>>>>> at first glance there nothing stopping,
>>>>>
>>>>> but since the plugin is framework specific,
>>>>> i also wonder, if it perhaps would have a good place under the pallets
>>>>> org
>>>>> (which has the flask ecosystem)
>>>>>
>>>>> -- 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/ed4f38bd/attachment.html>

From opensource at ronnypfannschmidt.de  Wed Sep 14 08:17:38 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Wed, 14 Sep 2016 14:17:38 +0200
Subject: [pytest-dev] transfer repo / pypi access / ML announce
In-Reply-To: <20160914115818.GY26884@uwanda>
References: <20160914115818.GY26884@uwanda>
Message-ID: <f1e17c31-e5a6-36c4-bbe2-106ea33e38a9@ronnypfannschmidt.de>

another point, we might want to introduce an pytest-attic org
and move unattended pytest-dev repos there based on primary
maintainership going away

-- Ronny


On 14.09.2016 13:58, holger krekel wrote:
> I am a bit concerned that people who transfer repos to pytest-dev think that it receives magic maintenance because this relevant section in the docs 
>
> http://doc.pytest.org/en/latest/contributing.html#submitting-plugins-to-pytest-dev
>
> is not very explicit about it, even says "sharing some of the maintenance responsibility".  I suggest we explicitely say that maintainers are generally expected to continue maintaining their plugins.
>
> And how about having a "pytest-dev" user which has release rights on pypi for all pytest-dev plugins?  The credentials could be shared in a file in our public repo, encrypted to known GPG public keys. Speaking of which, we could collect gpg keys of contributors in another file.
>
> lastly, if we had a pure pytest-announce mailing list we could announce new pytest-dev plugins (from time to time) and releases there. We can certainly get that list on python.org.
>
> best,
> holger
>
>
>
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/c865f78b/attachment-0001.html>

From holger at merlinux.eu  Wed Sep 14 09:42:40 2016
From: holger at merlinux.eu (holger krekel)
Date: Wed, 14 Sep 2016 15:42:40 +0200
Subject: [pytest-dev] transfer repo / pypi access / ML announce
In-Reply-To: <7b71e741-66ff-1ce2-7f17-cc90d0e1f04f@ronnypfannschmidt.de>
References: <20160914115818.GY26884@uwanda>
 <7b71e741-66ff-1ce2-7f17-cc90d0e1f04f@ronnypfannschmidt.de>
Message-ID: <20160914134240.GC26884@uwanda>

On Wed, Sep 14, 2016 at 14:01 +0200, Ronny Pfannschmidt wrote:
> sounds good to me,
> 
> can we up the release automation requirements,
> so git tag + travis deploys can be used for releasing?

FWIW i remain -0 on tag-triggers-release workflows.

holger

> best, Ronny
> 
> On 14.09.2016 13:58, holger krekel wrote:
> > I am a bit concerned that people who transfer repos to pytest-dev think that it receives magic maintenance because this relevant section in the docs 
> >
> > http://doc.pytest.org/en/latest/contributing.html#submitting-plugins-to-pytest-dev
> >
> > is not very explicit about it, even says "sharing some of the maintenance responsibility".  I suggest we explicitely say that maintainers are generally expected to continue maintaining their plugins.
> >
> > And how about having a "pytest-dev" user which has release rights on pypi for all pytest-dev plugins?  The credentials could be shared in a file in our public repo, encrypted to known GPG public keys. Speaking of which, we could collect gpg keys of contributors in another file.
> >
> > lastly, if we had a pure pytest-announce mailing list we could announce new pytest-dev plugins (from time to time) and releases there. We can certainly get that list on python.org.
> >
> > best,
> > holger
> >
> >
> >
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> 

From me at the-compiler.org  Wed Sep 14 09:48:05 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Wed, 14 Sep 2016 15:48:05 +0200
Subject: [pytest-dev] transfer repo / pypi access / ML announce
In-Reply-To: <20160914115818.GY26884@uwanda>
References: <20160914115818.GY26884@uwanda>
Message-ID: <20160914134805.6xg7u4gzfqywxzag@tonks>

Hey,

* holger krekel <holger at merlinux.eu> [2016-09-14 13:58:18 +0200]:
> I am a bit concerned that people who transfer repos to pytest-dev
> think that it receives magic maintenance

I read your sentence saying this does happen, and not that you're
concerned that it could happen, right?

If so, what makes you think that?

> lastly, if we had a pure pytest-announce mailing list we could
> announce new pytest-dev plugins (from time to time) and releases
> there. We can certainly get that list on python.org.

We already have testing-in-python, pytest-dev and python-announce, do
we really need a pytest-dev-announce too?

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/fe499f42/attachment.sig>

From basti at redtoad.de  Wed Sep 14 10:12:31 2016
From: basti at redtoad.de (Sebastian Rahlf)
Date: Wed, 14 Sep 2016 16:12:31 +0200
Subject: [pytest-dev] transfer repo / pypi access / ML announce
In-Reply-To: <7b71e741-66ff-1ce2-7f17-cc90d0e1f04f@ronnypfannschmidt.de>
References: <20160914115818.GY26884@uwanda>
 <7b71e741-66ff-1ce2-7f17-cc90d0e1f04f@ronnypfannschmidt.de>
Message-ID: <CAAQWEJ3y1w3hQV+VP42ke1o5Uyh=j=6mLHb5cFtzySLMCw4UpQ@mail.gmail.com>

Little word of caution: Not all plugins are on github/use git.
Travis will only work with github projects afaik.

Sebastian

2016-09-14 14:01 GMT+02:00 Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de>:

> sounds good to me,
>
> can we up the release automation requirements,
> so git tag + travis deploys can be used for releasing?
> best, Ronny
>
>
> On 14.09.2016 13:58, holger krekel wrote:
>
> I am a bit concerned that people who transfer repos to pytest-dev think that it receives magic maintenance because this relevant section in the docs
> http://doc.pytest.org/en/latest/contributing.html#submitting-plugins-to-pytest-dev
>
> is not very explicit about it, even says "sharing some of the maintenance responsibility".  I suggest we explicitely say that maintainers are generally expected to continue maintaining their plugins.
>
> And how about having a "pytest-dev" user which has release rights on pypi for all pytest-dev plugins?  The credentials could be shared in a file in our public repo, encrypted to known GPG public keys. Speaking of which, we could collect gpg keys of contributors in another file.
>
> lastly, if we had a pure pytest-announce mailing list we could announce new pytest-dev plugins (from time to time) and releases there. We can certainly get that list on python.org.
>
> best,
> holger
>
>
>
>
> _______________________________________________
> pytest-dev mailing listpytest-dev at python.orghttps://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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/14164094/attachment.html>

From rpfannsc at redhat.com  Wed Sep 14 10:35:25 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Wed, 14 Sep 2016 16:35:25 +0200
Subject: [pytest-dev] transfer repo / pypi access / ML announce
In-Reply-To: <CAAQWEJ3y1w3hQV+VP42ke1o5Uyh=j=6mLHb5cFtzySLMCw4UpQ@mail.gmail.com>
References: <20160914115818.GY26884@uwanda>
 <7b71e741-66ff-1ce2-7f17-cc90d0e1f04f@ronnypfannschmidt.de>
 <CAAQWEJ3y1w3hQV+VP42ke1o5Uyh=j=6mLHb5cFtzySLMCw4UpQ@mail.gmail.com>
Message-ID: <CAA10jzMpbM18BUPHDPYDxmSr1ZmjU-gS13vfjqMYjctdLSfA_Q@mail.gmail.com>

anything that can run deploy scripts works

-- Ronny

2016-09-14 16:12 GMT+02:00 Sebastian Rahlf <basti at redtoad.de>:

> Little word of caution: Not all plugins are on github/use git.
> Travis will only work with github projects afaik.
>
> Sebastian
>
> 2016-09-14 14:01 GMT+02:00 Ronny Pfannschmidt <
> opensource at ronnypfannschmidt.de>:
>
>> sounds good to me,
>>
>> can we up the release automation requirements,
>> so git tag + travis deploys can be used for releasing?
>> best, Ronny
>>
>>
>> On 14.09.2016 13:58, holger krekel wrote:
>>
>> I am a bit concerned that people who transfer repos to pytest-dev think that it receives magic maintenance because this relevant section in the docs
>> http://doc.pytest.org/en/latest/contributing.html#submitting-plugins-to-pytest-dev
>>
>> is not very explicit about it, even says "sharing some of the maintenance responsibility".  I suggest we explicitely say that maintainers are generally expected to continue maintaining their plugins.
>>
>> And how about having a "pytest-dev" user which has release rights on pypi for all pytest-dev plugins?  The credentials could be shared in a file in our public repo, encrypted to known GPG public keys. Speaking of which, we could collect gpg keys of contributors in another file.
>>
>> lastly, if we had a pure pytest-announce mailing list we could announce new pytest-dev plugins (from time to time) and releases there. We can certainly get that list on python.org.
>>
>> best,
>> holger
>>
>>
>>
>>
>> _______________________________________________
>> pytest-dev mailing listpytest-dev at python.orghttps://mail.python.org/mailman/listinfo/pytest-dev
>>
>>
>>
>> _______________________________________________
>> 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
>
>


-- 

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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/9c52db4f/attachment-0001.html>

From nicoddemus at gmail.com  Wed Sep 14 11:27:25 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 14 Sep 2016 15:27:25 +0000
Subject: [pytest-dev] transfer repo / pypi access / ML announce
In-Reply-To: <20160914115818.GY26884@uwanda>
References: <20160914115818.GY26884@uwanda>
Message-ID: <CA+RQFfcMrEdA7mXboyo7ZijGvz-coGc9v4VP_eRL-wnt7AFR9A@mail.gmail.com>

On Wed, Sep 14, 2016 at 8:58 AM holger krekel <holger at merlinux.eu> wrote:

> I am a bit concerned that people who transfer repos to pytest-dev think
> that it receives magic maintenance because this relevant section in the docs
>
>
> http://doc.pytest.org/en/latest/contributing.html#submitting-plugins-to-pytest-dev
>
> is not very explicit about it, even says "sharing some of the maintenance
> responsibility".  I suggest we explicitely say that maintainers are
> generally expected to continue maintaining their plugins.
>

No problem at all with changing the wording to make it more explicit. FWIW
so far most plugins in which I took care of the transfer continued to be
actively developed by their maintainers.

And how about having a "pytest-dev" user which has release rights on pypi
> for all pytest-dev plugins?  The credentials could be shared in a file in
> our public repo, encrypted to known GPG public keys. Speaking of which, we
> could collect gpg keys of contributors in another file.
>

Not sure, we need a "pytest-dev" user... isn't there a chance it might get
compromised?

Also, don't we need just usernames to add release rights to packages on
PyPI?

lastly, if we had a pure pytest-announce mailing list we could announce new
> pytest-dev plugins (from time to time) and releases there. We can certainly
> get that list on python.org.
>

As a person which occasionally discovers new plugins by browsing
plugincompat, if pytest-announce would be the place for people to announce
new plugins I would certainly subscribe to it. In my experience people
don't usually announce new plugins in TIP, and I don't subscribe to
announce because I couldn't keep track of all emails there.

Cheers,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/cb5e1558/attachment.html>

From holger at merlinux.eu  Wed Sep 14 12:33:57 2016
From: holger at merlinux.eu (holger krekel)
Date: Wed, 14 Sep 2016 18:33:57 +0200
Subject: [pytest-dev] transfer repo / pypi access / ML announce
In-Reply-To: <20160914134805.6xg7u4gzfqywxzag@tonks>
References: <20160914115818.GY26884@uwanda>
 <20160914134805.6xg7u4gzfqywxzag@tonks>
Message-ID: <20160914163357.GD26884@uwanda>

On Wed, Sep 14, 2016 at 15:48 +0200, Florian Bruhin wrote:
> Hey,
> 
> * holger krekel <holger at merlinux.eu> [2016-09-14 13:58:18 +0200]:
> > I am a bit concerned that people who transfer repos to pytest-dev
> > think that it receives magic maintenance
> 
> I read your sentence saying this does happen, and not that you're
> concerned that it could happen, right?
> 
> If so, what makes you think that?

we had a discussion on this at the sprint IIRC.  The contributing text is not explicit about it.  but if it isn't a real problem that's great - i don't know to be honest.
 
> > lastly, if we had a pure pytest-announce mailing list we could
> > announce new pytest-dev plugins (from time to time) and releases
> > there. We can certainly get that list on python.org.
> 
> We already have testing-in-python, pytest-dev and python-announce, do
> we really need a pytest-dev-announce too?

FYI on testing-in-python someone pushed for not having pytest dev micro releases announced and bruno/me agreed on only announcing minor/major releases.  

pytest-announce would be restricted and only used for pytest related announcements whereas testing-in-python is a discussion list and python-announce sees tons of announcements unrelated to pytest.

holger

From rpfannsc at redhat.com  Wed Sep 14 13:06:30 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Wed, 14 Sep 2016 19:06:30 +0200
Subject: [pytest-dev] transfer repo / pypi access / ML announce
In-Reply-To: <20160914163357.GD26884@uwanda>
References: <20160914115818.GY26884@uwanda>
 <20160914134805.6xg7u4gzfqywxzag@tonks>
 <20160914163357.GD26884@uwanda>
Message-ID: <CAA10jzOwXqmyxxyL=MSStT8s0msFz_mUrqmL=G9Gg6VFfUPW+Q@mail.gmail.com>

random thought - i do wonder if we should just publish a rss feed with the
releases

2016-09-14 18:33 GMT+02:00 holger krekel <holger at merlinux.eu>:

> On Wed, Sep 14, 2016 at 15:48 +0200, Florian Bruhin wrote:
> > Hey,
> >
> > * holger krekel <holger at merlinux.eu> [2016-09-14 13:58:18 +0200]:
> > > I am a bit concerned that people who transfer repos to pytest-dev
> > > think that it receives magic maintenance
> >
> > I read your sentence saying this does happen, and not that you're
> > concerned that it could happen, right?
> >
> > If so, what makes you think that?
>
> we had a discussion on this at the sprint IIRC.  The contributing text is
> not explicit about it.  but if it isn't a real problem that's great - i
> don't know to be honest.
>
> > > lastly, if we had a pure pytest-announce mailing list we could
> > > announce new pytest-dev plugins (from time to time) and releases
> > > there. We can certainly get that list on python.org.
> >
> > We already have testing-in-python, pytest-dev and python-announce, do
> > we really need a pytest-dev-announce too?
>
> FYI on testing-in-python someone pushed for not having pytest dev micro
> releases announced and bruno/me agreed on only announcing minor/major
> releases.
>
> pytest-announce would be restricted and only used for pytest related
> announcements whereas testing-in-python is a discussion list and
> python-announce sees tons of announcements unrelated to pytest.
>
> holger
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/82e01f20/attachment.html>

From opensource at ronnypfannschmidt.de  Sat Sep 17 04:10:19 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Sat, 17 Sep 2016 10:10:19 +0200
Subject: [pytest-dev] the move of pylib to github is technically finished
Message-ID: <a12c41fc-65c8-7cfa-6266-d2eec40af602@ronnypfannschmidt.de>

Hi all,


i finished the move to github and did a few simple fixups
in the process i learned various details, and fixed bugs in the
migration tool

now i feel confident i can do the same for tox in the afternoon.

i'll finish up the detail works with pylib and create issues wrt its
updating to pytest 3.x

then i#ll focus on tox


-- Ronny


From nicoddemus at gmail.com  Sat Sep 17 06:31:04 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 17 Sep 2016 10:31:04 +0000
Subject: [pytest-dev] the move of pylib to github is technically finished
In-Reply-To: <a12c41fc-65c8-7cfa-6266-d2eec40af602@ronnypfannschmidt.de>
References: <a12c41fc-65c8-7cfa-6266-d2eec40af602@ronnypfannschmidt.de>
Message-ID: <CA+RQFfcj6Gw=hTWqqPuyn3aZ=EKUQ3NiqkANFJbsV9hFWawqSg@mail.gmail.com>

Well done ronny! :)

On Sat, Sep 17, 2016, 05:10 Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

> Hi all,
>
>
> i finished the move to github and did a few simple fixups
> in the process i learned various details, and fixed bugs in the
> migration tool
>
> now i feel confident i can do the same for tox in the afternoon.
>
> i'll finish up the detail works with pylib and create issues wrt its
> updating to pytest 3.x
>
> then i#ll focus on tox
>
>
> -- 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160917/c96c0924/attachment.html>

From opensource at ronnypfannschmidt.de  Sat Sep 17 16:14:09 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Sat, 17 Sep 2016 22:14:09 +0200
Subject: [pytest-dev] tox is now on github
Message-ID: <f63d4a08-edd9-961d-4e5c-b4aea330d5ed@ronnypfannschmidt.de>

Hello everyone,

i am pleased to announce that after some setbacks
we now have finished the repository and
issue tracker migration for tox to github.

its new home is https://github.com/tox-dev/tox

due to the setbacks i ended up deferring various detail works (like travis/readthedocs)
those will be finished during the next few days.

even before the announcement the new place already started brimming with
activity 


-- Ronny


From opensource at ronnypfannschmidt.de  Sun Sep 18 07:05:13 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Sun, 18 Sep 2016 13:05:13 +0200
Subject: [pytest-dev] tox is now on github
In-Reply-To: <CAG5Cgtq_hyQHDK5fDH04ZbNeXG1M_B+QO-bPrFNtoV0nG6DOdw@mail.gmail.com>
References: <f63d4a08-edd9-961d-4e5c-b4aea330d5ed@ronnypfannschmidt.de>
 <CAG5Cgtq_hyQHDK5fDH04ZbNeXG1M_B+QO-bPrFNtoV0nG6DOdw@mail.gmail.com>
Message-ID: <e9e36099-e0bb-93a6-3e35-0b5e1eeaad18@ronnypfannschmidt.de>

Hi Oliver,

your pull request that was directly in the branch is already converted
to a branch on gh

for the 3 other ones, i am able to pull them and turn them into branches
however i wont be able to fix the references :/

i think i'd like to have a note from the authors if they prefer to do
the export on their own
or if they want to have a branch on GH to start off

cheers,
Ronny

On 18.09.2016 12:59, Oliver Bestwalter wrote:
> Hello Ronny,
>
> thanks a lot for going through the major PITA of doing such a move!
>
> One thing I noticed is that the 4 remaining pull requests have not
> been migrated. How can we deal with them?
>
> Also see: https://github.com/tox-dev/tox/issues/352#issuecomment-247791365
>
> The link to the pull request on Bitbucket now links to an unrelated
> issue on Github. Is that expected fallout from the move or would you
> have expected this to do the right thing on Github now?
>
> Cheers
> Oliver
>
> On Sat, 17 Sep 2016 at 22:14 Ronny Pfannschmidt
> <opensource at ronnypfannschmidt.de
> <mailto:opensource at ronnypfannschmidt.de>> wrote:
>
>     Hello everyone,
>
>     i am pleased to announce that after some setbacks
>     we now have finished the repository and
>     issue tracker migration for tox to github.
>
>     its new home is https://github.com/tox-dev/tox
>
>     due to the setbacks i ended up deferring various detail works
>     (like travis/readthedocs)
>     those will be finished during the next few days.
>
>     even before the announcement the new place already started
>     brimming with
>     activity
>
>
>     -- Ronny
>
>     _______________________________________________
>     pytest-dev mailing list
>     pytest-dev at python.org <mailto:pytest-dev at python.org>
>     https://mail.python.org/mailman/listinfo/pytest-dev
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160918/9fcf95d0/attachment.html>

From oliver at bestwalter.de  Sun Sep 18 07:34:33 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Sun, 18 Sep 2016 11:34:33 +0000
Subject: [pytest-dev] tox is now on github
In-Reply-To: <e9e36099-e0bb-93a6-3e35-0b5e1eeaad18@ronnypfannschmidt.de>
References: <f63d4a08-edd9-961d-4e5c-b4aea330d5ed@ronnypfannschmidt.de>
 <CAG5Cgtq_hyQHDK5fDH04ZbNeXG1M_B+QO-bPrFNtoV0nG6DOdw@mail.gmail.com>
 <e9e36099-e0bb-93a6-3e35-0b5e1eeaad18@ronnypfannschmidt.de>
Message-ID: <CAG5CgtpFbnz37TB3ZZh_OMyDG8bWFSQ32apQpvYUL4uhQjB0DQ@mail.gmail.com>

Hi Ronny,

nice. Those references won't really matter anymore, when the PRs are closed
and it's only a handful anyway.

What I would do now then is close my PR on BB and add a comment where it
has moved. Holger suggested to add a test for it, so it will still be open
for a while, till I get around to do that, as I have some other topics I
have to see to first.

Cheers
Oliver

On Sun, 18 Sep 2016 at 13:05 Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

> Hi Oliver,
>
> your pull request that was directly in the branch is already converted to
> a branch on gh
>
> for the 3 other ones, i am able to pull them and turn them into branches
> however i wont be able to fix the references :/
>
> i think i'd like to have a note from the authors if they prefer to do the
> export on their own
> or if they want to have a branch on GH to start off
>
> cheers,
> Ronny
> On 18.09.2016 12:59, Oliver Bestwalter wrote:
>
> Hello Ronny,
>
> thanks a lot for going through the major PITA of doing such a move!
>
> One thing I noticed is that the 4 remaining pull requests have not been
> migrated. How can we deal with them?
>
> Also see: https://github.com/tox-dev/tox/issues/352#issuecomment-247791365
>
> The link to the pull request on Bitbucket now links to an unrelated issue
> on Github. Is that expected fallout from the move or would you have
> expected this to do the right thing on Github now?
>
> Cheers
> Oliver
>
> On Sat, 17 Sep 2016 at 22:14 Ronny Pfannschmidt <
> opensource at ronnypfannschmidt.de> wrote:
>
>> Hello everyone,
>>
>> i am pleased to announce that after some setbacks
>> we now have finished the repository and
>> issue tracker migration for tox to github.
>>
>> its new home is https://github.com/tox-dev/tox
>>
>> due to the setbacks i ended up deferring various detail works (like
>> travis/readthedocs)
>> those will be finished during the next few days.
>>
>> even before the announcement the new place already started brimming with
>> activity
>>
>>
>> -- 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160918/8e20047b/attachment.html>

From oliver at bestwalter.de  Sun Sep 18 06:59:09 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Sun, 18 Sep 2016 10:59:09 +0000
Subject: [pytest-dev] tox is now on github
In-Reply-To: <f63d4a08-edd9-961d-4e5c-b4aea330d5ed@ronnypfannschmidt.de>
References: <f63d4a08-edd9-961d-4e5c-b4aea330d5ed@ronnypfannschmidt.de>
Message-ID: <CAG5Cgtq_hyQHDK5fDH04ZbNeXG1M_B+QO-bPrFNtoV0nG6DOdw@mail.gmail.com>

Hello Ronny,

thanks a lot for going through the major PITA of doing such a move!

One thing I noticed is that the 4 remaining pull requests have not been
migrated. How can we deal with them?

Also see: https://github.com/tox-dev/tox/issues/352#issuecomment-247791365

The link to the pull request on Bitbucket now links to an unrelated issue
on Github. Is that expected fallout from the move or would you have
expected this to do the right thing on Github now?

Cheers
Oliver

On Sat, 17 Sep 2016 at 22:14 Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

> Hello everyone,
>
> i am pleased to announce that after some setbacks
> we now have finished the repository and
> issue tracker migration for tox to github.
>
> its new home is https://github.com/tox-dev/tox
>
> due to the setbacks i ended up deferring various detail works (like
> travis/readthedocs)
> those will be finished during the next few days.
>
> even before the announcement the new place already started brimming with
> activity
>
>
> -- 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160918/7610f082/attachment-0001.html>

From tom at viner.tv  Tue Sep 20 15:33:19 2016
From: tom at viner.tv (Tom Viner)
Date: Tue, 20 Sep 2016 20:33:19 +0100
Subject: [pytest-dev] tox is now on github
Message-ID: <CANBSuyGGzyxSMJMySLT_-CJh9zBVwR3urKDTW534Kn4JjXkaAw@mail.gmail.com>

Hi Ronny,

Any plans to move detox as well? I've found that along with a local devpi
as a cache it can really speed up tox runs that have many envs.

It currently lives at:
https://bitbucket.org/hpk42/detox

Either way, I note that the PyPi description (
https://pypi.python.org/pypi/detox/ ) is now outdated as it links to the
tox issues on bitbucket, so I've made a PR to fix that:
https://bitbucket.org/hpk42/detox/pull-requests/5/

Cheers,
Tom

Date: Sat, 17 Sep 2016 22:14:09 +0200
> From: Ronny Pfannschmidt <opensource at ronnypfannschmidt.de>
> Hello everyone,
>
> i am pleased to announce that after some setbacks
> we now have finished the repository and
> issue tracker migration for tox to github.
>
> its new home is https://github.com/tox-dev/tox
>
> due to the setbacks i ended up deferring various detail works (like
> travis/readthedocs)
> those will be finished during the next few days.
>
> even before the announcement the new place already started brimming with
> activity
>
>
> -- Ronny
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160920/21c98abf/attachment.html>

From nicoddemus at gmail.com  Wed Sep 21 12:46:34 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 21 Sep 2016 16:46:34 +0000
Subject: [pytest-dev] pytest-warnings in 3.1
Message-ID: <CA+RQFffTmiieFofbxMydzviDDNkQPJc8-hCytMCdeuNbFKU__Q@mail.gmail.com>

Hi everyone,

During the sprint Florian Schulze developed pytest-warnings[1], and later
we decided to merge that into pytest 3.1.

I was trying to remember: did anybody volunteer to do that?

Cheers,

[1] https://github.com/fschulze/pytest-warnings
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160921/5b45bc65/attachment.html>

From opensource at ronnypfannschmidt.de  Thu Sep 22 04:00:44 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Thu, 22 Sep 2016 10:00:44 +0200
Subject: [pytest-dev] pytest-warnings in 3.1
In-Reply-To: <CA+RQFffTmiieFofbxMydzviDDNkQPJc8-hCytMCdeuNbFKU__Q@mail.gmail.com>
References: <CA+RQFffTmiieFofbxMydzviDDNkQPJc8-hCytMCdeuNbFKU__Q@mail.gmail.com>
Message-ID: <99edeece-98ff-0522-edf7-0e1a7927cd2c@ronnypfannschmidt.de>

im not aware of anyone signing up for that
as far as i remember there also was no further development on the plugin
itself


-- Ronny


On 21.09.2016 18:46, Bruno Oliveira wrote:
> Hi everyone,
>
> During the sprint Florian Schulze developed pytest-warnings[1], and
> later we decided to merge that into pytest 3.1.
>
> I was trying to remember: did anybody volunteer to do that?
>
> Cheers,
>
> [1] https://github.com/fschulze/pytest-warnings
>
>
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160922/136bb94c/attachment.html>

From mail at florian-schulze.net  Thu Sep 22 06:27:16 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Thu, 22 Sep 2016 12:27:16 +0200
Subject: [pytest-dev] pytest-warnings in 3.1
In-Reply-To: <99edeece-98ff-0522-edf7-0e1a7927cd2c@ronnypfannschmidt.de>
References: <CA+RQFffTmiieFofbxMydzviDDNkQPJc8-hCytMCdeuNbFKU__Q@mail.gmail.com>
 <99edeece-98ff-0522-edf7-0e1a7927cd2c@ronnypfannschmidt.de>
Message-ID: <2A437B70-4159-402D-A768-0105D3CBBCA2@florian-schulze.net>

Hi!

I didn't/don't have time at the moment. But besides a minor issue there 
isn't anything to do on the plugin.

In pytest itself we would have to replace the function calls with using 
the warnings module and gather those. We likely want to present pytest 
internal deprecations differently from in test warnings (the thing 
pytest-warnings does atm but doesn't separate).

Regards,
Florian Schulze

On 22 Sep 2016, at 10:00, Ronny Pfannschmidt wrote:

> im not aware of anyone signing up for that
> as far as i remember there also was no further development on the 
> plugin
> itself
>
> -- Ronny
>
> On 21.09.2016 18:46, Bruno Oliveira wrote:
>> Hi everyone,
>>
>> During the sprint Florian Schulze developed pytest-warnings[1], and
>> later we decided to merge that into pytest 3.1.
>>
>> I was trying to remember: did anybody volunteer to do that?
>>
>> Cheers,
>>
>> [1] https://github.com/fschulze/pytest-warnings
>>
>>
>> _______________________________________________
>> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160922/8eca217b/attachment.html>

From opensource at ronnypfannschmidt.de  Thu Sep 22 06:30:07 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Thu, 22 Sep 2016 12:30:07 +0200
Subject: [pytest-dev] pytest-warnings in 3.1
In-Reply-To: <2A437B70-4159-402D-A768-0105D3CBBCA2@florian-schulze.net>
References: <CA+RQFffTmiieFofbxMydzviDDNkQPJc8-hCytMCdeuNbFKU__Q@mail.gmail.com>
 <99edeece-98ff-0522-edf7-0e1a7927cd2c@ronnypfannschmidt.de>
 <2A437B70-4159-402D-A768-0105D3CBBCA2@florian-schulze.net>
Message-ID: <46c91d1f-4c8b-b669-8e60-0dffd850e5b9@ronnypfannschmidt.de>

Hi Florian,

thanks for the update.

im currently not too familiar with the internals myself

it seems like it will be slightly tricky to get right right,
as such i'd like to defer to 3.2 than end up in trouble right now

-- Ronny

On 22.09.2016 12:27, Florian Schulze wrote:
> Hi!
> I didn't/don't have time at the moment. But besides a minor issue
> there isn't anything to do on the plugin.
> In pytest itself we would have to replace the function calls with
> using the warnings module and gather those. We likely want to present
> pytest internal deprecations differently from in test warnings (the
> thing pytest-warnings does atm but doesn't separate).
> Regards,
> Florian Schulze
> On 22 Sep 2016, at 10:00, Ronny Pfannschmidt wrote:
>
>     im not aware of anyone signing up for that
>     as far as i remember there also was no further development on the
>     plugin itself
>
>
>     -- Ronny
>
>
>     On 21.09.2016 18:46, Bruno Oliveira wrote:
>>     Hi everyone,
>>
>>     During the sprint Florian Schulze developed pytest-warnings[1],
>>     and later we decided to merge that into pytest 3.1.
>>
>>     I was trying to remember: did anybody volunteer to do that?
>>
>>     Cheers,
>>
>>     [1] https://github.com/fschulze/pytest-warnings
>>
>>
>>     _______________________________________________
>>     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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160922/9ca736bd/attachment-0001.html>

From mail at florian-schulze.net  Thu Sep 22 06:40:19 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Thu, 22 Sep 2016 12:40:19 +0200
Subject: [pytest-dev] pytest-warnings in 3.1
In-Reply-To: <46c91d1f-4c8b-b669-8e60-0dffd850e5b9@ronnypfannschmidt.de>
References: <CA+RQFffTmiieFofbxMydzviDDNkQPJc8-hCytMCdeuNbFKU__Q@mail.gmail.com>
 <99edeece-98ff-0522-edf7-0e1a7927cd2c@ronnypfannschmidt.de>
 <2A437B70-4159-402D-A768-0105D3CBBCA2@florian-schulze.net>
 <46c91d1f-4c8b-b669-8e60-0dffd850e5b9@ronnypfannschmidt.de>
Message-ID: <9998D858-76E6-45B6-8642-7BD1134B2C13@florian-schulze.net>

I don't think it's urgent at all. The plugin works and pytest 
deprecations are visible since 3.0, the rest is just nice to have.

Regards,
Florian Schulze


On 22 Sep 2016, at 12:30, Ronny Pfannschmidt wrote:

> Hi Florian,
>
> thanks for the update.
>
> im currently not too familiar with the internals myself
>
> it seems like it will be slightly tricky to get right right,
> as such i'd like to defer to 3.2 than end up in trouble right now
>
> -- Ronny
>
> On 22.09.2016 12:27, Florian Schulze wrote:
>> Hi!
>> I didn't/don't have time at the moment. But besides a minor issue
>> there isn't anything to do on the plugin.
>> In pytest itself we would have to replace the function calls with
>> using the warnings module and gather those. We likely want to present
>> pytest internal deprecations differently from in test warnings (the
>> thing pytest-warnings does atm but doesn't separate).
>> Regards,
>> Florian Schulze
>> On 22 Sep 2016, at 10:00, Ronny Pfannschmidt wrote:
>>
>>     im not aware of anyone signing up for that
>>     as far as i remember there also was no further development on the
>>     plugin itself
>>
>>
>>     -- Ronny
>>
>>
>>     On 21.09.2016 18:46, Bruno Oliveira wrote:
>>>     Hi everyone,
>>>
>>>     During the sprint Florian Schulze developed pytest-warnings[1],
>>>     and later we decided to merge that into pytest 3.1.
>>>
>>>     I was trying to remember: did anybody volunteer to do that?
>>>
>>>     Cheers,
>>>
>>>     [1] https://github.com/fschulze/pytest-warnings
>>>
>>>
>>>     _______________________________________________
>>>     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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160922/a2ddb0cb/attachment.html>

From nicoddemus at gmail.com  Thu Sep 22 06:53:30 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 22 Sep 2016 10:53:30 +0000
Subject: [pytest-dev] pytest-warnings in 3.1
In-Reply-To: <9998D858-76E6-45B6-8642-7BD1134B2C13@florian-schulze.net>
References: <CA+RQFffTmiieFofbxMydzviDDNkQPJc8-hCytMCdeuNbFKU__Q@mail.gmail.com>
 <99edeece-98ff-0522-edf7-0e1a7927cd2c@ronnypfannschmidt.de>
 <2A437B70-4159-402D-A768-0105D3CBBCA2@florian-schulze.net>
 <46c91d1f-4c8b-b669-8e60-0dffd850e5b9@ronnypfannschmidt.de>
 <9998D858-76E6-45B6-8642-7BD1134B2C13@florian-schulze.net>
Message-ID: <CA+RQFffKKvTrUi0qgGRkLVLxrkkW0CQyLZ=ZzzDBU3-Ek8n_2A@mail.gmail.com>

On Thu, Sep 22, 2016 at 7:40 AM Florian Schulze <mail at florian-schulze.net>
wrote:

> I don't think it's urgent at all. The plugin works and pytest deprecations
> are visible since 3.0, the rest is just nice to have.
>

Oh I agree it is not urgent. I was just asking because we didn't really
make any progress yet towards 3.1, and that was a topic that wasn't very
clear to me if someone had volunteered to it.

Thanks for the feedback guys!

Cheers,
Bruno.


Regards,
> Florian Schulze
> On 22 Sep 2016, at 12:30, Ronny Pfannschmidt wrote:
>
> Hi Florian,
>
> thanks for the update.
>
> im currently not too familiar with the internals myself
>
> it seems like it will be slightly tricky to get right right,
> as such i'd like to defer to 3.2 than end up in trouble right now
>
> -- Ronny
> On 22.09.2016 12:27, Florian Schulze wrote:
>
> Hi!
> I didn't/don't have time at the moment. But besides a minor issue there
> isn't anything to do on the plugin.
> In pytest itself we would have to replace the function calls with using
> the warnings module and gather those. We likely want to present pytest
> internal deprecations differently from in test warnings (the thing
> pytest-warnings does atm but doesn't separate).
> Regards,
> Florian Schulze
> On 22 Sep 2016, at 10:00, Ronny Pfannschmidt wrote:
>
> im not aware of anyone signing up for that
> as far as i remember there also was no further development on the plugin
> itself
>
>
> -- Ronny
>
> On 21.09.2016 18:46, Bruno Oliveira wrote:
>
> Hi everyone,
>
> During the sprint Florian Schulze developed pytest-warnings[1], and later
> we decided to merge that into pytest 3.1.
>
> I was trying to remember: did anybody volunteer to do that?
>
> Cheers,
>
> [1] https://github.com/fschulze/pytest-warnings
>
>
> _______________________________________________
> pytest-dev mailing listpytest-dev at python.orghttps://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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160922/52f8985d/attachment.html>

From opensource at ronnypfannschmidt.de  Thu Sep 22 08:15:15 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Thu, 22 Sep 2016 14:15:15 +0200
Subject: [pytest-dev] the sorry state of pylib tests and pylib
Message-ID: <8a5a68e4-a97c-8f83-abe9-df1eb1ae2ecf@ronnypfannschmidt.de>

Hi everyone,

while fixing up some pylib tests i noticed a set of massive issues

a) all py.code related tests are completely broken on pytest 3.0

b) the svn related tests are completely broken and outdated (can we kill
it?)

c) depending on environment there are massive issues with pylib path
encodings

as far as i can tell thats just scratching the surface


im not yet sure what to do about it, but some thing has to be done ^^


-- Ronny



From nicoddemus at gmail.com  Tue Sep 27 08:51:58 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 27 Sep 2016 12:51:58 +0000
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <8a5a68e4-a97c-8f83-abe9-df1eb1ae2ecf@ronnypfannschmidt.de>
References: <8a5a68e4-a97c-8f83-abe9-df1eb1ae2ecf@ronnypfannschmidt.de>
Message-ID: <CA+RQFfeiY6JdQqz3nxsWeh6eXe19P+Zj7+tDJ2N7p9tO_MWsbQ@mail.gmail.com>

Hi Ronny,

How long do we plan to maintain pylib? Perhaps we can get rid of stuff we
no longer wish to maintain (svn, py.code) and release a 2.0 version? If
someone still needs that functionality, they can pin it.

Not sure about the py.path encoding errors you mention though.

Cheers,

On Thu, Sep 22, 2016 at 9:16 AM Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

> Hi everyone,
>
> while fixing up some pylib tests i noticed a set of massive issues
>
> a) all py.code related tests are completely broken on pytest 3.0
>
> b) the svn related tests are completely broken and outdated (can we kill
> it?)
>
> c) depending on environment there are massive issues with pylib path
> encodings
>
> as far as i can tell thats just scratching the surface
>
>
> im not yet sure what to do about it, but some thing has to be done ^^
>
>
> -- 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160927/9b526ba0/attachment.html>

From opensource at ronnypfannschmidt.de  Tue Sep 27 09:06:55 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Tue, 27 Sep 2016 15:06:55 +0200
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <CA+RQFfeiY6JdQqz3nxsWeh6eXe19P+Zj7+tDJ2N7p9tO_MWsbQ@mail.gmail.com>
References: <8a5a68e4-a97c-8f83-abe9-df1eb1ae2ecf@ronnypfannschmidt.de>
 <CA+RQFfeiY6JdQqz3nxsWeh6eXe19P+Zj7+tDJ2N7p9tO_MWsbQ@mail.gmail.com>
Message-ID: <642bac31-82a2-c59c-ab91-e071755c81ef@ronnypfannschmidt.de>

HI Bruno,

as things stand we have to maintain it until py.test no longer depends on it

a 2.0 release that kills py.code is a non-option as any project
dependign on ot will be limited in py.test version

my plan is to de-vendor bits of pylib (like iniconfig, apipkg)

some have been lone projects at the beginning anyway (apipkg and
iniconfig got only vendored due to the bad state of packaging

stuff like svn can be removed as it is completely broken

basically once we de-vendored the bits we use and removed the py.path
dependency of pytest,
we can put pylib into a abandoned state

but before that *eek*

-- Ronny



On 27.09.2016 14:51, Bruno Oliveira wrote:
> Hi Ronny,
>
> How long do we plan to maintain pylib? Perhaps we can get rid of stuff
> we no longer wish to maintain (svn, py.code) and release a 2.0
> version? If someone still needs that functionality, they can pin it.
>
> Not sure about the py.path encoding errors you mention though.
>
> Cheers,
>
> On Thu, Sep 22, 2016 at 9:16 AM Ronny Pfannschmidt
> <opensource at ronnypfannschmidt.de
> <mailto:opensource at ronnypfannschmidt.de>> wrote:
>
>     Hi everyone,
>
>     while fixing up some pylib tests i noticed a set of massive issues
>
>     a) all py.code related tests are completely broken on pytest 3.0
>
>     b) the svn related tests are completely broken and outdated (can
>     we kill
>     it?)
>
>     c) depending on environment there are massive issues with pylib path
>     encodings
>
>     as far as i can tell thats just scratching the surface
>
>
>     im not yet sure what to do about it, but some thing has to be done ^^
>
>
>     -- Ronny
>
>
>     _______________________________________________
>     pytest-dev mailing list
>     pytest-dev at python.org <mailto:pytest-dev at python.org>
>     https://mail.python.org/mailman/listinfo/pytest-dev
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160927/de264811/attachment.html>

From nicoddemus at gmail.com  Tue Sep 27 09:59:16 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 27 Sep 2016 13:59:16 +0000
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <642bac31-82a2-c59c-ab91-e071755c81ef@ronnypfannschmidt.de>
References: <8a5a68e4-a97c-8f83-abe9-df1eb1ae2ecf@ronnypfannschmidt.de>
 <CA+RQFfeiY6JdQqz3nxsWeh6eXe19P+Zj7+tDJ2N7p9tO_MWsbQ@mail.gmail.com>
 <642bac31-82a2-c59c-ab91-e071755c81ef@ronnypfannschmidt.de>
Message-ID: <CA+RQFffuQ_FhPxOXOeBr2Ri5BkXAqxVpo_6uovw-R6ZvL5LqUA@mail.gmail.com>

On Tue, Sep 27, 2016 at 10:07 AM Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

> as things stand we have to maintain it until py.test no longer depends on
> it
>
> a 2.0 release that kills py.code is a non-option as any project dependign
> on ot will be limited in py.test version
>

Don't we already vendor py.code in pytest? That makes it independent from
what's installed on the system, at least as far as py.code is concerned. My
idea was just to remove parts which py.test does not use or is vendored in
(svn and py.code come to mind).


> my plan is to de-vendor bits of pylib (like iniconfig, apipkg)
>
You mean remove them from pylib and publish them as isolated packages?

How do others feel about having pytest depend on more packages? I'm usually
fine about it, but would like to know others opinions.

some have been lone projects at the beginning anyway (apipkg and iniconfig
> got only vendored due to the bad state of packaging
>
> stuff like svn can be removed as it is completely broken
> basically once we de-vendored the bits we use and removed the py.path
> dependency of pytest,
> we can put pylib into a abandoned state
>

About py.path, we could implement a backward compatible interface which is
implemented as a thin layer in terms of pathlib (I think we discussed this
on GTalk some other day).

Cheers,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160927/892055ce/attachment.html>

From opensource at ronnypfannschmidt.de  Tue Sep 27 10:13:57 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Tue, 27 Sep 2016 16:13:57 +0200
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <CA+RQFffuQ_FhPxOXOeBr2Ri5BkXAqxVpo_6uovw-R6ZvL5LqUA@mail.gmail.com>
References: <8a5a68e4-a97c-8f83-abe9-df1eb1ae2ecf@ronnypfannschmidt.de>
 <CA+RQFfeiY6JdQqz3nxsWeh6eXe19P+Zj7+tDJ2N7p9tO_MWsbQ@mail.gmail.com>
 <642bac31-82a2-c59c-ab91-e071755c81ef@ronnypfannschmidt.de>
 <CA+RQFffuQ_FhPxOXOeBr2Ri5BkXAqxVpo_6uovw-R6ZvL5LqUA@mail.gmail.com>
Message-ID: <25fea567-9ff6-b3f5-3bec-8983b9ea58e6@ronnypfannschmidt.de>



On 27.09.2016 15:59, Bruno Oliveira wrote:
> On Tue, Sep 27, 2016 at 10:07 AM Ronny Pfannschmidt
> <opensource at ronnypfannschmidt.de
> <mailto:opensource at ronnypfannschmidt.de>> wrote:
>
>     as things stand we have to maintain it until py.test no longer
>     depends on it
>
>     a 2.0 release that kills py.code is a non-option as any project
>     dependign on ot will be limited in py.test version
>
>
> Don't we already vendor py.code in pytest? That makes it independent
> from what's installed on the system, at least as far as py.code is
> concerned. My idea was just to remove parts which py.test does not use
> or is vendored in (svn and py.code come to mind).
>  
we vendored it to since changing its api in pylib would break down-streams
if we now remove it we break down-streams just the same
and we could just have put it into a separate package to begin with
>
>     my plan is to de-vendor bits of pylib (like iniconfig, apipkg)
>
> You mean remove them from pylib and publish them as isolated packages? 
>
correct, the main reason to pull in things like iniconfig and apipkg
was, bad packaging tooling 6-7 years ago
its much better now

> How do others feel about having pytest depend on more packages? I'm
> usually fine about it, but would like to know others opinions.
>
>     some have been lone projects at the beginning anyway (apipkg and
>     iniconfig got only vendored due to the bad state of packaging
>
>     stuff like svn can be removed as it is completely broken
>
>     basically once we de-vendored the bits we use and removed the
>     py.path dependency of pytest,
>     we can put pylib into a abandoned state
>
>
> About py.path, we could implement a backward compatible interface
> which is implemented as a thin layer in terms of pathlib (I think we
> discussed this on GTalk some other day).
thats one of the plans
but i would like to eventually get rid of the api alltogether,
we couldnt push it when we had the chance, and now pathlib is the standard

>
> Cheers,
> Bruno.

cheers,
Ronny

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160927/41407aee/attachment-0001.html>

From nicoddemus at gmail.com  Tue Sep 27 10:25:43 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 27 Sep 2016 14:25:43 +0000
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <25fea567-9ff6-b3f5-3bec-8983b9ea58e6@ronnypfannschmidt.de>
References: <8a5a68e4-a97c-8f83-abe9-df1eb1ae2ecf@ronnypfannschmidt.de>
 <CA+RQFfeiY6JdQqz3nxsWeh6eXe19P+Zj7+tDJ2N7p9tO_MWsbQ@mail.gmail.com>
 <642bac31-82a2-c59c-ab91-e071755c81ef@ronnypfannschmidt.de>
 <CA+RQFffuQ_FhPxOXOeBr2Ri5BkXAqxVpo_6uovw-R6ZvL5LqUA@mail.gmail.com>
 <25fea567-9ff6-b3f5-3bec-8983b9ea58e6@ronnypfannschmidt.de>
Message-ID: <CA+RQFfcDB6Y-q4dzco9GNJNn=P-uVcoB6WmxKwNJEkX-TcqxRA@mail.gmail.com>

On Tue, Sep 27, 2016 at 11:14 AM Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

>
>
> On 27.09.2016 15:59, Bruno Oliveira wrote:
>
> On Tue, Sep 27, 2016 at 10:07 AM Ronny Pfannschmidt <
> opensource at ronnypfannschmidt.de> wrote:
>
>> as things stand we have to maintain it until py.test no longer depends on
>> it
>>
>> a 2.0 release that kills py.code is a non-option as any project dependign
>> on ot will be limited in py.test version
>>
>
> Don't we already vendor py.code in pytest? That makes it independent from
> what's installed on the system, at least as far as py.code is concerned. My
> idea was just to remove parts which py.test does not use or is vendored in
> (svn and py.code come to mind).
>
>
> we vendored it to since changing its api in pylib would break down-streams
> if we now remove it we break down-streams just the same
>

Yes, but those downstream projects would have the option o pinning to pylib
< 2. Plus I think there must be almost no projects using it, it seems very
pytest specific, that was one of the reasonings we used to justify
vendoring py.code into pytest in the first place.

and we could just have put it into a separate package to begin with
>

One of the reasons to vendor it was to make it easier to fix bugs on it
without having to apply the fix in a separate library and make a separate
release; just moving py.code to a separate package would not help with
that.

my plan is to de-vendor bits of pylib (like iniconfig, apipkg)
>>
> You mean remove them from pylib and publish them as isolated packages?
>
> correct, the main reason to pull in things like iniconfig and apipkg was,
> bad packaging tooling 6-7 years ago
> its much better now
>

I see, but that would break downstream projects which use those
sub-packages as well, right? Note that I'm fine to do that in a 2.0 release.


> About py.path, we could implement a backward compatible interface which is
> implemented as a thin layer in terms of pathlib (I think we discussed this
> on GTalk some other day).
>
> thats one of the plans
> but i would like to eventually get rid of the api alltogether,
> we couldnt push it when we had the chance, and now pathlib is the standard
>

Sure, but removing that API is a very long term plan IMHO because tons of
code depend on it (tmpdir is certainly a very popular fixture) so I
wouldn't dare remove it in the next few years.

We could eventually introduce a separate fixture which provides the pathlib
interface, and eventually move tmpdir to a separate plugin for legacy code
to use. But this would be very down the road in my opinion.

Cheers,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160927/28a281fb/attachment.html>

From opensource at ronnypfannschmidt.de  Tue Sep 27 10:32:10 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Tue, 27 Sep 2016 16:32:10 +0200
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <CA+RQFfcDB6Y-q4dzco9GNJNn=P-uVcoB6WmxKwNJEkX-TcqxRA@mail.gmail.com>
References: <8a5a68e4-a97c-8f83-abe9-df1eb1ae2ecf@ronnypfannschmidt.de>
 <CA+RQFfeiY6JdQqz3nxsWeh6eXe19P+Zj7+tDJ2N7p9tO_MWsbQ@mail.gmail.com>
 <642bac31-82a2-c59c-ab91-e071755c81ef@ronnypfannschmidt.de>
 <CA+RQFffuQ_FhPxOXOeBr2Ri5BkXAqxVpo_6uovw-R6ZvL5LqUA@mail.gmail.com>
 <25fea567-9ff6-b3f5-3bec-8983b9ea58e6@ronnypfannschmidt.de>
 <CA+RQFfcDB6Y-q4dzco9GNJNn=P-uVcoB6WmxKwNJEkX-TcqxRA@mail.gmail.com>
Message-ID: <3c7cfd8d-31a6-fbe5-8c0f-092dc7d6f66d@ronnypfannschmidt.de>



On 27.09.2016 16:25, Bruno Oliveira wrote:
>
>
> On Tue, Sep 27, 2016 at 11:14 AM Ronny Pfannschmidt
> <opensource at ronnypfannschmidt.de
> <mailto:opensource at ronnypfannschmidt.de>> wrote:
>
>
>
>     On 27.09.2016 15:59, Bruno Oliveira wrote:
>>     On Tue, Sep 27, 2016 at 10:07 AM Ronny Pfannschmidt
>>     <opensource at ronnypfannschmidt.de
>>     <mailto:opensource at ronnypfannschmidt.de>> wrote:
>>
>>         as things stand we have to maintain it until py.test no
>>         longer depends on it
>>
>>         a 2.0 release that kills py.code is a non-option as any
>>         project dependign on ot will be limited in py.test version
>>
>>
>>     Don't we already vendor py.code in pytest? That makes it
>>     independent from what's installed on the system, at least as far
>>     as py.code is concerned. My idea was just to remove parts which
>>     py.test does not use or is vendored in (svn and py.code come to
>>     mind).
>>      
>     we vendored it to since changing its api in pylib would break
>     down-streams
>     if we now remove it we break down-streams just the same
>
>
> Yes, but those downstream projects would have the option o pinning to
> pylib < 2. Plus I think there must be almost no projects using it, it
> seems very pytest specific, that was one of the reasonings we used to
> justify vendoring py.code into pytest in the first place.
>
>     and we could just have put it into a separate package to begin with
>
>
> One of the reasons to vendor it was to make it easier to fix bugs on
> it without having to apply the fix in a separate library and make a
> separate release; just moving py.code to a separate package would not
> help with that. 
>
well, the fact that we need more than 5 minutes to do a release is
concerning - i#d prefer if we could handle that differently
but well, vendoring py.code  destroyed most tests for py.code in pylib,
and we cant yet abandon pylib

by now i think it would be much more easy to separate py.code and and
prepare to either freeze or evolve it
>
>>         my plan is to de-vendor bits of pylib (like iniconfig, apipkg)
>>
>>     You mean remove them from pylib and publish them as isolated
>>     packages? 
>>
>     correct, the main reason to pull in things like iniconfig and
>     apipkg was, bad packaging tooling 6-7 years ago
>     its much better now
>
>
> I see, but that would break downstream projects which use those
> sub-packages as well, right? Note that I'm fine to do that in a 2.0
> release.
pylib can just expose them the same way it exposes py.test,
the main problem is stable api
>  
>
>>     About py.path, we could implement a backward compatible interface
>>     which is implemented as a thin layer in terms of pathlib (I think
>>     we discussed this on GTalk some other day).
>     thats one of the plans
>     but i would like to eventually get rid of the api alltogether,
>     we couldnt push it when we had the chance, and now pathlib is the
>     standard
>
>
> Sure, but removing that API is a very long term plan IMHO because tons
> of code depend on it (tmpdir is certainly a very popular fixture) so I
> wouldn't dare remove it in the next few years. 
>
> We could eventually introduce a separate fixture which provides the
> pathlib interface, and eventually move tmpdir to a separate plugin for
> legacy code to use. But this would be very down the road in my opinion.
>
> Cheers,
> Bruno.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160927/b4c433bc/attachment.html>

From me at the-compiler.org  Tue Sep 27 12:07:56 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 27 Sep 2016 18:07:56 +0200
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <3c7cfd8d-31a6-fbe5-8c0f-092dc7d6f66d@ronnypfannschmidt.de>
 <CA+RQFfcDB6Y-q4dzco9GNJNn=P-uVcoB6WmxKwNJEkX-TcqxRA@mail.gmail.com>
Message-ID: <20160927160756.r5pjjsljwprdemvw@tonks>

* Bruno Oliveira <nicoddemus at gmail.com> [2016-09-27 14:25:43 +0000]:
> Yes, but those downstream projects would have the option o pinning to pylib
> < 2. Plus I think there must be almost no projects using it, it seems very
> pytest specific, that was one of the reasonings we used to justify
> vendoring py.code into pytest in the first place.

At least in Debian, only pytest and some pytest-plugins have a reverse
dependency on it:

pytest, pytest-cov, pytest-django, pytest-instafail, pytest-pylint,
pytest-xdist

I also really can't find anything significant with a few GitHub
searches either.

> Sure, but removing that API is a very long term plan IMHO because tons of
> code depend on it (tmpdir is certainly a very popular fixture) so I
> wouldn't dare remove it in the next few years.
> 
> We could eventually introduce a separate fixture which provides the pathlib
> interface, and eventually move tmpdir to a separate plugin for legacy code
> to use. But this would be very down the road in my opinion.

I think the plan we discussed somewhere (here? At the sprint?) is
having a compat layer over pathlib (with the things nobody hopefully
uses, like the svn stuff removed), and then having a configuration
option people could switch to have normal pathlib.Path objects
instead. I know it's something I'd do in my testsuite! ;)

* Ronny Pfannschmidt <opensource at ronnypfannschmidt.de> [2016-09-27 16:32:10 +0200]:
> but well, vendoring py.code  destroyed most tests for py.code in pylib,
> and we cant yet abandon pylib

If we don't find any non-pytest project using it, why not?

> >>         my plan is to de-vendor bits of pylib (like iniconfig, apipkg)
> >>
> >>     You mean remove them from pylib and publish them as isolated
> >>     packages? 
> >>
> >     correct, the main reason to pull in things like iniconfig and
> >     apipkg was, bad packaging tooling 6-7 years ago
> >     its much better now
> >
> >
> > I see, but that would break downstream projects which use those
> > sub-packages as well, right? Note that I'm fine to do that in a 2.0
> > release.
> pylib can just expose them the same way it exposes py.test,
> the main problem is stable api

FWIW it also generates some overhead for downstream distribution
packagers if every distribution suddenly needs to package a handful of
new dependencies for everything ;)

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160927/89afb069/attachment.sig>

From opensource at ronnypfannschmidt.de  Tue Sep 27 12:13:28 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Tue, 27 Sep 2016 18:13:28 +0200
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <20160927160756.r5pjjsljwprdemvw@tonks>
References: <20160927160756.r5pjjsljwprdemvw@tonks>
Message-ID: <9C84D6A8-36C4-40DD-9684-419CFD64F957@ronnypfannschmidt.de>

Various distros debundle already, at least apipkg is severely outdated and a mess
-- Ronny

Am 27. September 2016 18:07:56 MESZ, schrieb Florian Bruhin <me at the-compiler.org>:
>* Bruno Oliveira <nicoddemus at gmail.com> [2016-09-27 14:25:43 +0000]:
>> Yes, but those downstream projects would have the option o pinning to
>pylib
>> < 2. Plus I think there must be almost no projects using it, it seems
>very
>> pytest specific, that was one of the reasonings we used to justify
>> vendoring py.code into pytest in the first place.
>
>At least in Debian, only pytest and some pytest-plugins have a reverse
>dependency on it:
>
>pytest, pytest-cov, pytest-django, pytest-instafail, pytest-pylint,
>pytest-xdist
>
>I also really can't find anything significant with a few GitHub
>searches either.
>
>> Sure, but removing that API is a very long term plan IMHO because
>tons of
>> code depend on it (tmpdir is certainly a very popular fixture) so I
>> wouldn't dare remove it in the next few years.
>> 
>> We could eventually introduce a separate fixture which provides the
>pathlib
>> interface, and eventually move tmpdir to a separate plugin for legacy
>code
>> to use. But this would be very down the road in my opinion.
>
>I think the plan we discussed somewhere (here? At the sprint?) is
>having a compat layer over pathlib (with the things nobody hopefully
>uses, like the svn stuff removed), and then having a configuration
>option people could switch to have normal pathlib.Path objects
>instead. I know it's something I'd do in my testsuite! ;)
>
>* Ronny Pfannschmidt <opensource at ronnypfannschmidt.de> [2016-09-27
>16:32:10 +0200]:
>> but well, vendoring py.code  destroyed most tests for py.code in
>pylib,
>> and we cant yet abandon pylib
>
>If we don't find any non-pytest project using it, why not?
>
>> >>         my plan is to de-vendor bits of pylib (like iniconfig,
>apipkg)
>> >>
>> >>     You mean remove them from pylib and publish them as isolated
>> >>     packages? 
>> >>
>> >     correct, the main reason to pull in things like iniconfig and
>> >     apipkg was, bad packaging tooling 6-7 years ago
>> >     its much better now
>> >
>> >
>> > I see, but that would break downstream projects which use those
>> > sub-packages as well, right? Note that I'm fine to do that in a 2.0
>> > release.
>> pylib can just expose them the same way it exposes py.test,
>> the main problem is stable api
>
>FWIW it also generates some overhead for downstream distribution
>packagers if every distribution suddenly needs to package a handful of
>new dependencies for everything ;)
>
>Florian
>
>-- 
>http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>         I love long mails! | http://email.is-not-s.ms/

From holger at merlinux.eu  Tue Sep 27 12:21:25 2016
From: holger at merlinux.eu (holger krekel)
Date: Tue, 27 Sep 2016 18:21:25 +0200
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <8a5a68e4-a97c-8f83-abe9-df1eb1ae2ecf@ronnypfannschmidt.de>
References: <8a5a68e4-a97c-8f83-abe9-df1eb1ae2ecf@ronnypfannschmidt.de>
Message-ID: <20160927162125.GY9334@uwanda>

Hi Ronny, everyone,

i had actually replied to this mail a few days ago but it got lost due to my playing around with new mail setups and clients :/

So here is my 2cent collection IIRC:

- IMO py is in low-effort maintenance mode.  Removing anything is likely
  to break things, increase maintenance effort -> not worth it.

- pylib could in tox.ini for testing just depend on pytest<3.0 and be done with it.  That's probably good enough for the next 1-2 years.

- meanwhile pytest can rather aim to vendor/get rid of things like we did with py.code.  A big thing probably here is py.path.local usage.  Maybe writing a wrapper around pathlib with py.path.local API would be a good not too cumbersome strategy because it doesn't touch much code.

best,
holger



On Thu, Sep 22, 2016 at 14:15 +0200, Ronny Pfannschmidt wrote:
> Hi everyone,
> 
> while fixing up some pylib tests i noticed a set of massive issues
> 
> a) all py.code related tests are completely broken on pytest 3.0
> 
> b) the svn related tests are completely broken and outdated (can we kill
> it?)
> 
> c) depending on environment there are massive issues with pylib path
> encodings
> 
> as far as i can tell thats just scratching the surface
> 
> 
> im not yet sure what to do about it, but some thing has to be done ^^
> 
> 
> -- Ronny
> 
> 
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From holger at merlinux.eu  Tue Sep 27 12:30:35 2016
From: holger at merlinux.eu (holger krekel)
Date: Tue, 27 Sep 2016 18:30:35 +0200
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <20160927160756.r5pjjsljwprdemvw@tonks>
References: <3c7cfd8d-31a6-fbe5-8c0f-092dc7d6f66d@ronnypfannschmidt.de>
 <CA+RQFfcDB6Y-q4dzco9GNJNn=P-uVcoB6WmxKwNJEkX-TcqxRA@mail.gmail.com>
 <20160927160756.r5pjjsljwprdemvw@tonks>
Message-ID: <20160927163035.GZ9334@uwanda>

On Tue, Sep 27, 2016 at 18:07 +0200, Florian Bruhin wrote:
> * Bruno Oliveira <nicoddemus at gmail.com> [2016-09-27 14:25:43 +0000]:
> > Yes, but those downstream projects would have the option o pinning to pylib
> > < 2. Plus I think there must be almost no projects using it, it seems very
> > pytest specific, that was one of the reasonings we used to justify
> > vendoring py.code into pytest in the first place.
> 
> At least in Debian, only pytest and some pytest-plugins have a reverse
> dependency on it:
> 
> pytest, pytest-cov, pytest-django, pytest-instafail, pytest-pylint,
> pytest-xdist

do you mean that in debian no packages depend on py?  What about tox to begin with?  

> I also really can't find anything significant with a few GitHub
> searches either.

and FWIW github searches shows a lot of hits for py.path.local() at least:

https://github.com/search?utf8=%E2%9C%93&q=%22py.path.local%22++extension%3Apy&type=Code&ref=searchresults

or do you really mean just "py.code"? 

holger

> > Sure, but removing that API is a very long term plan IMHO because tons of
> > code depend on it (tmpdir is certainly a very popular fixture) so I
> > wouldn't dare remove it in the next few years.
> > 
> > We could eventually introduce a separate fixture which provides the pathlib
> > interface, and eventually move tmpdir to a separate plugin for legacy code
> > to use. But this would be very down the road in my opinion.
> 
> I think the plan we discussed somewhere (here? At the sprint?) is
> having a compat layer over pathlib (with the things nobody hopefully
> uses, like the svn stuff removed), and then having a configuration
> option people could switch to have normal pathlib.Path objects
> instead. I know it's something I'd do in my testsuite! ;)
> 
> * Ronny Pfannschmidt <opensource at ronnypfannschmidt.de> [2016-09-27 16:32:10 +0200]:
> > but well, vendoring py.code  destroyed most tests for py.code in pylib,
> > and we cant yet abandon pylib
> 
> If we don't find any non-pytest project using it, why not?
> 
> > >>         my plan is to de-vendor bits of pylib (like iniconfig, apipkg)
> > >>
> > >>     You mean remove them from pylib and publish them as isolated
> > >>     packages? 
> > >>
> > >     correct, the main reason to pull in things like iniconfig and
> > >     apipkg was, bad packaging tooling 6-7 years ago
> > >     its much better now
> > >
> > >
> > > I see, but that would break downstream projects which use those
> > > sub-packages as well, right? Note that I'm fine to do that in a 2.0
> > > release.
> > pylib can just expose them the same way it exposes py.test,
> > the main problem is stable api
> 
> FWIW it also generates some overhead for downstream distribution
> packagers if every distribution suddenly needs to package a handful of
> new dependencies for everything ;)
> 
> Florian
> 
> -- 
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>          I love long mails! | http://email.is-not-s.ms/



> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


From me at the-compiler.org  Tue Sep 27 12:42:21 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 27 Sep 2016 18:42:21 +0200
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <20160927163035.GZ9334@uwanda>
References: <3c7cfd8d-31a6-fbe5-8c0f-092dc7d6f66d@ronnypfannschmidt.de>
 <CA+RQFfcDB6Y-q4dzco9GNJNn=P-uVcoB6WmxKwNJEkX-TcqxRA@mail.gmail.com>
 <20160927160756.r5pjjsljwprdemvw@tonks>
 <20160927163035.GZ9334@uwanda>
Message-ID: <20160927164220.6ejlo7oa7g4bcusq@tonks>

* holger krekel <holger at merlinux.eu> [2016-09-27 18:30:35 +0200]:
> On Tue, Sep 27, 2016 at 18:07 +0200, Florian Bruhin wrote:
> > * Bruno Oliveira <nicoddemus at gmail.com> [2016-09-27 14:25:43 +0000]:
> > > Yes, but those downstream projects would have the option o pinning to pylib
> > > < 2. Plus I think there must be almost no projects using it, it seems very
> > > pytest specific, that was one of the reasonings we used to justify
> > > vendoring py.code into pytest in the first place.
> > 
> > At least in Debian, only pytest and some pytest-plugins have a reverse
> > dependency on it:
> > 
> > pytest, pytest-cov, pytest-django, pytest-instafail, pytest-pylint,
> > pytest-xdist
> 
> do you mean that in debian no packages depend on py?  What about tox to begin with?  

Oh, my bad - seems like apt-rdepends only shows packages installed
locally, and I apparently don't have tox installed on that machine...

> > I also really can't find anything significant with a few GitHub
> > searches either.
> 
> and FWIW github searches shows a lot of hits for py.path.local() at least:
> 
> https://github.com/search?utf8=%E2%9C%93&q=%22py.path.local%22++extension%3Apy&type=Code&ref=searchresults

All those _metainfo.py matches are vendored
dependencies/eggs/virtualenvs in the repositories - this is the
_metainfo.py which is part of pylib.

I digged a bit deeper and found those matches:
- udir.py in cffi's testsuite
- nullpath.py as part of pypy/rpython
- test_linker.py as part of pylib
- conftest.py in various pytest testsuites
- confpath.py as part of pypy

After that I kind of gave up - but you're right that py.path probably
is in more widespread use than I thought.

https://github.com/search?utf8=%E2%9C%93&q=%22py.path.local%22++extension%3Apy+-filename%3A_metainfo.py+-filename%3Audir.py+-filename%3Anullpath.py+-filename%3Atest_linker.py+-filename%3Aconftest.py+-filename%3Aconfpath.py&type=Code

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160927/dccd68d8/attachment-0001.sig>

From opensource at ronnypfannschmidt.de  Tue Sep 27 13:27:35 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Tue, 27 Sep 2016 19:27:35 +0200
Subject: [pytest-dev] the sorry state of pylib tests and pylib
In-Reply-To: <20160927162125.GY9334@uwanda>
References: <8a5a68e4-a97c-8f83-abe9-df1eb1ae2ecf@ronnypfannschmidt.de>
 <20160927162125.GY9334@uwanda>
Message-ID: <eb3d5238-320e-53ec-dcb9-1a6b14d63f72@ronnypfannschmidt.de>

Hi Holger,

over the course of the next few months i'd like to run the following
actions on pylib

1. de-vendor apipkg - the version last released has bugfixes and works
in bpython (low efford)
2. de-vendor iniconfig - that allows to get rid of the pylib dependency
more easily (i already did a release, low to medium effort)
3. remove the svn paths (they are broken and nobody is stepping up to
fix them)
    im considering making a call for participation on that one (low to
medium effort)

-- Ronny

On 27.09.2016 18:21, holger krekel wrote:

> Hi Ronny, everyone,
>
> i had actually replied to this mail a few days ago but it got lost due to my playing around with new mail setups and clients :/
>
> So here is my 2cent collection IIRC:
>
> - IMO py is in low-effort maintenance mode.  Removing anything is likely
>   to break things, increase maintenance effort -> not worth it.
>
> - pylib could in tox.ini for testing just depend on pytest<3.0 and be done with it.  That's probably good enough for the next 1-2 years.
>
> - meanwhile pytest can rather aim to vendor/get rid of things like we did with py.code.  A big thing probably here is py.path.local usage.  Maybe writing a wrapper around pathlib with py.path.local API would be a good not too cumbersome strategy because it doesn't touch much code.
>
> best,
> holger
>
>
>
> On Thu, Sep 22, 2016 at 14:15 +0200, Ronny Pfannschmidt wrote:
>> Hi everyone,
>>
>> while fixing up some pylib tests i noticed a set of massive issues
>>
>> a) all py.code related tests are completely broken on pytest 3.0
>>
>> b) the svn related tests are completely broken and outdated (can we kill
>> it?)
>>
>> c) depending on environment there are massive issues with pylib path
>> encodings
>>
>> as far as i can tell thats just scratching the surface
>>
>>
>> im not yet sure what to do about it, but some thing has to be done ^^
>>
>>
>> -- Ronny
>>
>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev



From nicoddemus at gmail.com  Thu Sep 29 17:55:18 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 29 Sep 2016 21:55:18 +0000
Subject: [pytest-dev] pytest 3.0.3 released!
Message-ID: <CA+RQFfcgKsPkwBS9kN88CVUnniucYkp+7tG2cRjoEO_1uicyTA@mail.gmail.com>

Hello everyone,

pytest 3.0.3 has just been released to PyPI.

This release fixes some regressions and bugs reported in the last version,
being a drop-in replacement. To upgrade::

  pip install --upgrade pytest

The changelog is available at http://doc.pytest.org/en/latest/changelog.html
.

Thanks to all who contributed to this release, among them:

* Bruno Oliveira
* Florian Bruhin
* Floris Bruynooghe
* Huayi Zhang
* Lev Maximov
* Raquel Alegre
* Ronny Pfannschmidt
* Roy Williams
* Tyler Goodlet
* mbyt

Happy testing,
The pytest Development Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160929/6d58e0ba/attachment.html>

From emil.petersen at thalmic.com  Fri Sep 30 17:26:03 2016
From: emil.petersen at thalmic.com (Emil Petersen)
Date: Fri, 30 Sep 2016 17:26:03 -0400
Subject: [pytest-dev] How to repeat tests with a setup-action before each
 repitition
Message-ID: <B04A96F7-DDFE-43A8-BC2F-C9434FD62A4B@thalmic.com>

Hello pytest-dev,

I am looking to repeat some of the tests in my test suite, and want to call a certain action before each repetition. To be clear, I want to:

1) First, run all the tests marked with repeat, as-is
2) Then, take a specific action, in this case rebooting a device
3) Then, repeat each test marked with repeat
4) Then, repeat steps 2-3 the amount of times specified.

The reason I want to run step #2 before every ?repeat? is because step #2 is expensive, but needs to be performed before the tests are called. 

So my ideal code might look something like this (not real code):

@pytest.mark.repeat
def test_something()
    check_something == last_result_from_file()

@pytest.mark.repeat
def test_something_else:
    something_else()

def expensive_setup():
    set_up()

Using the above as an example, I want to run test_something and test_something_else, then expensive_setup, then the two tests again, then expensive_setup, etc. So only one call to expensive_setup for each run including test_something() and test_something_else()

What would be a sensible way to go about this?

As an addendum, it is ideal if each test is only reported as -one- test, rather than one test being generated for each run. But this last thing I imagine/hope I can do in some of the reporting hooks. Ideally, if any one call to the functions ends up generating a failure or error, it would be able to fail, and abort any attempts at subsequently running (I.e. failures should be final).

However, I?ve found no satisfactory way to do the above. Can anyone provide some pointers about a good way to go about this?

In case you?re curious about why the tests need to be repeated, it?s to hunt for race conditions, and other failures which may occur sometimes.

Thank you for your time.

Kind Regards,
-- 
Emil Petersen | Software Test Engineer
 <https://www.thalmic.com/>
T: 1-888-777-2546 x692 <>     E: emil.petersen at thalmic.com <mailto:victoria.baskerville at thalmic.com>

-- 
----
CONFIDENTIALITY NOTICE:  This communication, and any attachments thereto, 
is confidential and intended solely for use by the recipient(s) named above.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160930/afbe1a84/attachment.html>