On 08.08.2016 16:08, Floris Bruynooghe wrote:
On 8 August 2016 at 06:48, Ronny Pfannschmidt
wrote:
That would break external code
Uhm, so we've committed to mainting py._code in two places? Makes me
wonder what the motivation to merge into pytest was.
no, pylib will no longer evolve, its a
On 8 August 2016 at 06:48, Ronny Pfannschmidt
wrote:
> That would break external code
Uhm, so we've committed to mainting py._code in two places? Makes me
wonder what the motivation to merge into pytest was.
> Pylib is maintenance-only
While it's not terribly actively developed there's still s
That would break external code
Pylib is maintenance-only
-- Ronny
Am 8. August 2016 00:43:50 MESZ, schrieb Floris Bruynooghe :
>Hi,
>
>We did move the py._code library over to pytest._code a little while
>ago, I wasn't really involved so don't remember the details. But
>seems it was never remov
Hi,
We did move the py._code library over to pytest._code a little while
ago, I wasn't really involved so don't remember the details. But
seems it was never removed from the py library itself. Was this on
purpose? Do we want to maintain two versions of this code?
Reason I'm asking is because t
