pytest-2.7.2: bug fixes
===
pytest is a mature Python testing tool with more than a 1100 tests
against itself, passing on many different interpreters and platforms.
This release is supposed to be drop-in compatible to 2.7.1.
See below for the changes and see docs at:
http
* holger krekel [2015-06-23 13:43:47 +]:
> On Tue, Jun 23, 2015 at 14:25 +0100, Floris Bruynooghe wrote:
> > On 20 June 2015 at 16:37, Anatoly Bubenkov wrote:
> > > How about slack for notifications and chat?
> > >
> > >
> > > On 15:42, Sat, Jun 20, 2015 Tom Viner wrote:
> > >>
> > >> +1 for
nice catch!
On Tue, Jun 23, 2015 at 3:06 PM Florian Bruhin wrote:
> * Floris Bruynooghe [2015-06-23 13:54:09 +0100]:
> > On 16 June 2015 at 03:20, Anatoly Bubenkov wrote:
> > > after such a success with pytest move, should we start the same
> process for
> > > other repos under pytest-dev on b
On Tue, Jun 23, 2015 at 14:25 +0100, Floris Bruynooghe wrote:
> On 20 June 2015 at 16:37, Anatoly Bubenkov wrote:
> > How about slack for notifications and chat?
> >
> >
> > On 15:42, Sat, Jun 20, 2015 Tom Viner wrote:
> >>
> >> +1 for Gitter. Really reduces the barrier to entry for people to eng
On 20 June 2015 at 16:37, Anatoly Bubenkov wrote:
> How about slack for notifications and chat?
>
>
> On 15:42, Sat, Jun 20, 2015 Tom Viner wrote:
>>
>> +1 for Gitter. Really reduces the barrier to entry for people to engage.
Could gitter bridge bi-directionally with IRC on freenode? There is
* Floris Bruynooghe [2015-06-23 13:54:09 +0100]:
> On 16 June 2015 at 03:20, Anatoly Bubenkov wrote:
> > after such a success with pytest move, should we start the same process for
> > other repos under pytest-dev on bb?
>
> Not sure if anyone saw my tweet, but I noticed (sadly too late!) that
>
cleaning up the repo and leaving the readme with redirect seems like a good
plan - just like we need for pytest on old location under Holger's account
On Tue, Jun 23, 2015 at 2:51 PM Floris Bruynooghe wrote:
> Hi,
>
> I noticed Bruno created an issue to say that they should now be
> reported on
but it's not neccessary (or most likely not) because of the problematic
migration
the way git and hg store changes is still different, git always store full
file contents on any change to it from revision to revision, while hg i
believe uses some periodic snapshotting mechanism, so it does full cop
On 16 June 2015 at 03:20, Anatoly Bubenkov wrote:
> after such a success with pytest move, should we start the same process for
> other repos under pytest-dev on bb?
Not sure if anyone saw my tweet, but I noticed (sadly too late!) that
the git repo seems to be ~50Mb to clone instead of ~20Mb for
Hi,
I noticed Bruno created an issue to say that they should now be
reported on github instead. I was wondering if we should maybe simply
disable issue tracking completely? I've just experimented with this
in a test repo and it seems you can no longer access issues when you
disable it, however i
10 matches
Mail list logo
