From builds at drone.io  Fri Sep  4 11:54:37 2015
From: builds at drone.io (Drone.io Build)
Date: Fri, 04 Sep 2015 09:54:37 +0000
Subject: [Pytest-commit] [FAIL] py - # 23
Message-ID: <20150904095436.114754.43468@drone.io>

Build Failed

Build      : https://drone.io/bitbucket.org/pytest-dev/py/23
Project    : https://drone.io/bitbucket.org/pytest-dev/py

Repository : https://bitbucket.org/pytest-dev/py
Version    : 2308:b9cdab378c58
Author     : Floris Bruynooghe <flub at devork.be>
Branch     : default

Message:
Merged in b-enlnt/py/issue70 (pull request #32)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-commit/attachments/20150904/f1566dbf/attachment.html>

From builds at drone.io  Fri Sep  4 12:03:56 2015
From: builds at drone.io (Drone.io Build)
Date: Fri, 04 Sep 2015 10:03:56 +0000
Subject: [Pytest-commit] [FAIL] py - # 22
Message-ID: <20150904095349.11264.28629@drone.io>

Build Failed

Build      : https://drone.io/bitbucket.org/pytest-dev/py/22
Project    : https://drone.io/bitbucket.org/pytest-dev/py

Repository : https://bitbucket.org/pytest-dev/py
Version    : 2308:b9cdab378c58
Author     : Floris Bruynooghe <flub at devork.be>
Branch     : default

Message:
Merged in b-enlnt/py/issue70 (pull request #32)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-commit/attachments/20150904/724e801f/attachment.html>

From issues-reply at bitbucket.org  Fri Sep 11 20:57:05 2015
From: issues-reply at bitbucket.org (Michael Nazario)
Date: Fri, 11 Sep 2015 18:57:05 -0000
Subject: [Pytest-commit] Issue #273: Support conda envs when using Miniconda
	(hpk42/tox)
Message-ID: <20150911185705.8019.96806@app14.ash-private.bitbucket.org>

New issue 273: Support conda envs when using Miniconda
https://bitbucket.org/hpk42/tox/issues/273/support-conda-envs-when-using-miniconda

Michael Nazario:

**Miniconda** provides conda envs to create isolated Python environments similar to `virtualenv`. Its main advantage is that conda environments also isolate the binary shared library dependencies from the rest of your machine. Unfortunately, conda does not support virtualenvs because of the difference in how they manage shared libraries.

Since Miniconda isolates its shared library dependencies from the rest of your machine, **virtualenvs which are created by a Miniconda-based environment fail during creation time**. The virtualenvs will attempt to use shared libraries in the system-level location, but not the Miniconda location.

**NOTE:** If you try to create virtualenvs using Miniconda in an environment which already has the correct shared libraries in the system-level location, then your virtualenv will *seem* to succeed. However, any shared libraries which were only installed using conda will fail at runtime. Because of this, testing this feature should be done in an isolated environment.

I believe that the first implementation of this feature has these requirements:

 * Create conda environments instead of virtualenvs *based on a single miniconda Python version*
 * Install pip using conda by default
 * Add dependencies using pip (like virtualenvs)

Further features which are necessary for complete conda env supports are:

 * Create conda environments for multiple miniconda Python versions
 * Allow the installation of conda packages along with pip packages

There is a similar project called ctox (https://github.com/hayd/ctox) which tries to implement this. However, it doesn't have any guarantees on reliability. This project was actually started around the time there were comments on this ticket (https://bitbucket.org/hpk42/tox/issues/167/add-an-option-to-run-commands-after) about conda.

I would like to work with the tox team on specifying any additions necessary for conda support in Tox.



From issues-reply at bitbucket.org  Wed Sep 23 12:43:23 2015
From: issues-reply at bitbucket.org (Christer van der Meeren)
Date: Wed, 23 Sep 2015 10:43:23 -0000
Subject: [Pytest-commit] Issue #274: Specify compiler (hpk42/tox)
Message-ID: <20150923104323.24324.86342@app06.ash-private.bitbucket.org>

New issue 274: Specify compiler
https://bitbucket.org/hpk42/tox/issues/274/specify-compiler

Christer van der Meeren:

I'm on Windows and developing a package that needs to be built with MinGW (e.g. python setup.py install --compiler=mingw32). I have tried but not found any way to specify the compiler when using tox. Is this possible?



From issues-reply at bitbucket.org  Wed Sep 30 05:53:05 2015
From: issues-reply at bitbucket.org (Javier Ruere)
Date: Wed, 30 Sep 2015 03:53:05 -0000
Subject: [Pytest-commit] Issue #772: The load_tests protocol from unittest
 is not supported (pytest-dev/pytest)
Message-ID: <20150930035305.31027.78355@app11.ash-private.bitbucket.org>

New issue 772: The load_tests protocol from unittest is not supported
https://bitbucket.org/pytest-dev/pytest/issues/772/the-load_tests-protocol-from-unittest-is

Javier Ruere:

It would be very convenient to support the mentioned protocol as then py.test would be a more complete drop in replacement for the unittest test runner.

https://docs.python.org/2/library/unittest.html#load-tests-protocol