On Thu, Sep 17, 2015 at 9:37 AM holger krekel wrote:
> The one "flakes" env failing for the wheel has to do with the cx_freeze
> tests which were run with the "sdist" pacckage, the latter pollutes the
> testing directory which then lets flakes fail. I think cx_freeze should
On Thu, Sep 17, 2015 at 14:53 +0200, Ronny Pfannschmidt wrote:
> Can you review the 2.8 milestone on. Gh?
I'll take a brief look and see what can be done within my time limits
however, i think we shouldn't block 2.8 for any of the issues -- it
already contains more changes and fixes/improvements
Hi Florian, all,
i am finally getting back into coding/project work again.
FWIW i think we should get 2.8 out the door ASAP. Before
i can help much with it i need to get new devpi releases out
and i am not sure at the moment how much work that is.
If anyone can point me to where my
Hi Holger,
Glad to have you back. :)
The main points holding back 2.8 I think are:
* vendoring pluggy (https://github.com/pytest-dev/pytest/pull/959)
* merge pytest-cache into core (
https://github.com/pytest-dev/pytest/pull/828)
Cheers,
Bruno.
On Mon, Sep 7, 2015 at 5:16 AM holger krekel
On Tue, Aug 25, 2015 at 12:34 PM Floris Bruynooghe f...@devork.be wrote:
On 25 August 2015 at 14:10, Floris Bruynooghe f...@devork.be wrote:
On 25 August 2015 at 12:58, Bruno Oliveira nicodde...@gmail.com wrote:
How about:
* Create a script which fetches the latest pluggy version, and
Hello,
On 9 August 2015 at 23:45, Bruno Oliveira nicodde...@gmail.com wrote:
Hi,
I also think we should release 2.8 directly.
Yes, a release which supports python 3.5 would be nice. AFAIK we
could just release 2.7.3 without any work so if someone wants to
release that I think you should just
Hi,
I also think we should release 2.8 directly.
There are a couple of issues/PRs that should go into 2.8, IMO:
- Merge pytest-cache into core (
https://github.com/pytest-dev/pytest/pull/828); I think Ronny is working on
this;
- Release pytest-xdist 1.13, so we can merge non-zero exit code if
Hi!
We've been talking about doing a release since somewhen before
EuroPython and there's still no release with Python 3.5 support out
yet ;)
What's missing for a 2.7.3, and what for 2.8.0? Does it make sense to
release 2.7.3, or should we go for 2.8.0 directly?
Looking at the changelog, 2.8