From issues-reply at bitbucket.org  Mon Dec  1 20:19:03 2014
From: issues-reply at bitbucket.org (Travis Johnson)
Date: Mon, 01 Dec 2014 19:19:03 -0000
Subject: [Pytest-commit] Issue #636: Error in example documentation for
	fixtures (hpk42/pytest)
Message-ID: <20141201191903.13587.37061@app10.ash-private.bitbucket.org>

New issue 636: Error in example documentation for fixtures
https://bitbucket.org/hpk42/pytest/issue/636/error-in-example-documentation-for

Travis Johnson:

This statement: https://bitbucket.org/hpk42/pytest/src/d91265465608bd3777ab0c882e5d68335d7472dd/doc/en/fixture.txt?at=default#cl-100
is false, the test failure provided for the example fails on the line *before* the `assert 0` for some unrelated reason. Personally I think just removing the `assert "merlinux" in msg` line and re-producing the test failure output should be good, fixing what appears to be a bug is a bit out of scope.



From issues-reply at bitbucket.org  Wed Dec  3 16:51:29 2014
From: issues-reply at bitbucket.org (gcc111)
Date: Wed, 03 Dec 2014 15:51:29 -0000
Subject: [Pytest-commit] Issue #637: Assertion reverse engineering often
	fails (hpk42/pytest)
Message-ID: <20141203155129.1511.66046@app08.ash-private.bitbucket.org>

New issue 637: Assertion reverse engineering often fails
https://bitbucket.org/hpk42/pytest/issue/637/assertion-reverse-engineering-often-fails

gcc111:

Consider the following simple program:

```
#!python
var = None
def test_foo():
    assert 'Hello' == var, "whee"
```

I get the following output from py.test:

	======================================================= test session starts ========================================================
	platform linux2 -- Python 2.7.3 -- py-1.4.22 -- pytest-2.6.0
	plugins: django-assets, django
	collected 0 items / 1 errors 

	============================================================== ERRORS ==============================================================
	________________________________________ ERROR collecting ../../../../../../../tmp/test.py _________________________________________
	/tmp/test.py:3: in <module>
	    assert 'Hello' == var, "whee"
	E   AssertionError: whee
	===================================================== 1 error in 0.06 seconds ======================================================

Which is very pretty, but didn't actually tell me what went wrong, by giving me the values of the left and right hand sides of the assertion.

I have to switch back to UnitTest.assertEqual, which does tell me (when I set longMessage = True):

	Traceback (most recent call last):
	  File "test.py", line 9, in test_foo
	    self.assertEqual('Hello', var, "whee")
	AssertionError: 'Hello' != None : whee




From issues-reply at bitbucket.org  Thu Dec  4 00:38:31 2014
From: issues-reply at bitbucket.org (Eric Dand)
Date: Wed, 03 Dec 2014 23:38:31 -0000
Subject: [Pytest-commit] Issue #638: python.py:813 (in "parametrize") raises
 "TypeError: object of type 'int' has no len()" in some cases (hpk42/pytest)
Message-ID: <20141203233831.16139.51141@app03.ash-private.bitbucket.org>

New issue 638: python.py:813 (in "parametrize") raises "TypeError: object of type 'int' has no len()" in some cases
https://bitbucket.org/hpk42/pytest/issue/638/pythonpy-813-in-parametrize-raises

Eric Dand:

Passing a one-element array for `argnames` and an array of `int`s as `argvalues` to `parametrize` causes the `assert` at line 813 to fail. This is only caused by this edge case:

- If `argnames` is a single-element string (ie. no commas, not enclosed in an array), 788-791 will try to split argnames by commas, find at 790 that `len(argnames) == 1`, and will box up `argvalues`'s values into tuples. 
- If `argnames` is an array that has more than one element, each element of `argvalues` should be a tuple. This is then the intended behaviour, and therefore not an issue.
- If `argnames` is a single-element array, however, it sidesteps the check at 788, `if not isinstance(argnames, (tuple, list)):`, wrongly assuming there is more than one element in `argname`, and therefore does not pack up `argvalues` into tuples.

The simplest fix is to simply dedent lines 790 and 791 to check the length of argnames regardless of whether it was passed as a string or not. I'm not sure if this change is entirely safe, but it did resolve the issue in my case.



From issues-reply at bitbucket.org  Mon Dec  8 16:53:41 2014
From: issues-reply at bitbucket.org (fabiofz)
Date: Mon, 08 Dec 2014 15:53:41 -0000
Subject: [Pytest-commit] Issue #639: conftest being loaded twice (giving
 internal error) or not found depending on how pytest is called
 (hpk42/pytest)
Message-ID: <20141208155341.13233.45598@app06.ash-private.bitbucket.org>

New issue 639: conftest being loaded twice (giving internal error) or not found depending on how pytest is called
https://bitbucket.org/hpk42/pytest/issue/639/conftest-being-loaded-twice-giving

fabiofz:

I've uploaded a project to github with the structure to reproduce the issue:

https://github.com/fabioz/check_pytest

The file: https://github.com/fabioz/check_pytest/blob/master/pack/tests/test_fixtures.py has the details.

As a resume, when I go to the tests folder and run the test_fixtures, it seems I can't get pytest to load the conftest file properly... either it finds it twice and reports an error (if I pass the full-path) or it doesn't find it at all if I pass a relative path to the working dir.



From issues-reply at bitbucket.org  Wed Dec 10 11:34:14 2014
From: issues-reply at bitbucket.org (ivanmalison)
Date: Wed, 10 Dec 2014 10:34:14 -0000
Subject: [Pytest-commit] Issue #640: Easy way to spit out all the failing
 test names as plain text (hpk42/pytest)
Message-ID: <20141210103414.18715.25802@app12.ash-private.bitbucket.org>

New issue 640: Easy way to spit out all the failing test names as plain text
https://bitbucket.org/hpk42/pytest/issue/640/easy-way-to-spit-out-all-the-failing-test

ivanmalison:

This seems like a such a basic and obvious feature, but I've scoured the documentation and I can't seem to find any mention of how to do this.



From issues-reply at bitbucket.org  Thu Dec 11 08:12:17 2014
From: issues-reply at bitbucket.org (Michael Howitz)
Date: Thu, 11 Dec 2014 07:12:17 -0000
Subject: [Pytest-commit] Issue #641: MemoryError when writing junitxml for
 large test suite (hpk42/pytest)
Message-ID: <20141211071217.4683.16693@app06.ash-private.bitbucket.org>

New issue 641: MemoryError when writing junitxml for large test suite
https://bitbucket.org/hpk42/pytest/issue/641/memoryerror-when-writing-junitxml-for

Michael Howitz:

In a large project (> 3500 Tests) we get a MemoryError when writing the junit xml file.
(The host is our Jenkins CI server with 4 GB of RAM and 3 GB of swap.)

```
#!python

bin/py.test --nosugar --junitxml=parts/tests.xml --cov-report html --cov-report xml --cov-report term --cov src
============================= test session starts ==============================
platform linux2 -- Python 2.7.6 -- py-1.4.25 -- pytest-2.6.4
plugins: gocept.pytestlayer, cache, cov, sugar, remove-stale-bytecode
collected 3643 items

? Many, many tests which ran fine ?

Traceback (most recent call last):
  File "bin/py.test", line 308, in <module>
    sys.exit(pytest.main())
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/config.py", line 41, in main
    return config.hook.pytest_cmdline_main(config=config)
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/core.py", line 413, in __call__
    return self._docall(methods, kwargs)
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/core.py", line 424, in _docall
    res = mc.execute()
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/core.py", line 315, in execute
    res = method(**kwargs)
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/main.py", line 116, in pytest_cmdline_main
    return wrap_session(config, _main)
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/main.py", line 109, in wrap_session
    exitstatus=session.exitstatus)
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/core.py", line 413, in __call__
    return self._docall(methods, kwargs)
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/core.py", line 424, in _docall
    res = mc.execute()
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/core.py", line 315, in execute
    res = method(**kwargs)
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/terminal.py", line 349, in pytest_sessionfinish
    __multicall__.execute()
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/core.py", line 315, in execute
    res = method(**kwargs)
  File "/srv/jenkins/eggs/pytest-2.6.4-py2.7.egg/_pytest/junitxml.py", line 215, in pytest_sessionfinish
    ).unicode(indent=0))
  File "/srv/jenkins/eggs/py-1.4.25-py2.7.egg/py/_xmlgen.py", line 54, in unicode
    return u("").join(l)
MemoryError
```

Any suggestions?



From issues-reply at bitbucket.org  Thu Dec 11 11:43:05 2014
From: issues-reply at bitbucket.org (Thomas Tanner)
Date: Thu, 11 Dec 2014 10:43:05 -0000
Subject: [Pytest-commit] Issue #642: misleading error report (hpk42/pytest)
Message-ID: <20141211104305.3291.43975@app04.ash-private.bitbucket.org>

New issue 642: misleading error report
https://bitbucket.org/hpk42/pytest/issue/642/misleading-error-report

Thomas Tanner:

py.test doesn't show the code section which is actually failing

```
#!python

platform darwin -- Python 2.7.8 -- py-1.4.26 -- pytest-2.6.4
plugins: pythonpath
collected 1 items

test_with.py F

=================================================== FAILURES ===================================================
_____________________________________________________ test _____________________________________________________

    def test():
        from pytest import raises
        with raises(AssertionError):
            if True:
                pass
            else:
>               pass
E               Failed: DID NOT RAISE

test_with.py:7: Failed
```



From commits-noreply at bitbucket.org  Thu Dec 11 12:13:39 2014
From: commits-noreply at bitbucket.org (commits-noreply at bitbucket.org)
Date: Thu, 11 Dec 2014 11:13:39 -0000
Subject: [Pytest-commit] commit/tox: 2 new changesets
Message-ID: <20141211111339.6226.50134@app07.ash-private.bitbucket.org>

2 new commits in tox:

https://bitbucket.org/hpk42/tox/commits/b0e448bae10b/
Changeset:   b0e448bae10b
User:        leinz
Date:        2014-12-02 08:03:48+00:00
Summary:     Determine Jenkins environment as described in docs
HUDSON_URL is still checked for backward compatibility.
Affected #:  1 file

diff -r cc3723fe6680f49ec11995d8df7f37b533fc5f33 -r b0e448bae10bcf28dd717d10010658bda138e4d5 tox/_config.py
--- a/tox/_config.py
+++ b/tox/_config.py
@@ -802,7 +802,7 @@
         return ps.yield_words
 
 def getcontextname():
-    if 'HUDSON_URL' in os.environ:
+    if any(env in os.environ for env in ['JENKINS_URL', 'HUDSON_URL']):
         return 'jenkins'
     return None
 


https://bitbucket.org/hpk42/tox/commits/361530d6b080/
Changeset:   361530d6b080
User:        leinz
Date:        2014-12-10 21:37:30+00:00
Summary:     Add test for getcontextname()
Affected #:  1 file

diff -r b0e448bae10bcf28dd717d10010658bda138e4d5 -r 361530d6b08048d678cf8a585bac67553eddaba7 tests/test_config.py
--- a/tests/test_config.py
+++ b/tests/test_config.py
@@ -148,6 +148,20 @@
     assert get_homedir() == "123"
 
 
+class TestGetcontextname:
+    def test_blank(self, monkeypatch):
+        monkeypatch.setattr(os, "environ", {})
+        assert getcontextname() is None
+
+    def test_jenkins(self, monkeypatch):
+        monkeypatch.setattr(os, "environ", {"JENKINS_URL": "xyz"})
+        assert getcontextname() == "jenkins"
+
+    def test_hudson_legacy(self, monkeypatch):
+        monkeypatch.setattr(os, "environ", {"HUDSON_URL": "xyz"})
+        assert getcontextname() == "jenkins"
+
+
 class TestIniParser:
     def test_getdefault_single(self, tmpdir, newconfig):
         config = newconfig("""

Repository URL: https://bitbucket.org/hpk42/tox/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

From commits-noreply at bitbucket.org  Thu Dec 11 12:14:31 2014
From: commits-noreply at bitbucket.org (commits-noreply at bitbucket.org)
Date: Thu, 11 Dec 2014 11:14:31 -0000
Subject: [Pytest-commit] commit/tox: hpk42: refine determination if we run
 from Jenkins, thanks Borge Lanes.
Message-ID: <20141211111431.25587.81279@app11.ash-private.bitbucket.org>

1 new commit in tox:

https://bitbucket.org/hpk42/tox/commits/7109f1184d9f/
Changeset:   7109f1184d9f
User:        hpk42
Date:        2014-12-11 11:14:24+00:00
Summary:     refine determination if we run from Jenkins, thanks Borge Lanes.
Affected #:  1 file

diff -r 361530d6b08048d678cf8a585bac67553eddaba7 -r 7109f1184d9f0303b050fce006cd90fa3db9e26e CHANGELOG
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -8,6 +8,8 @@
 
 - fix issue199: fill resultlog structure ahead of virtualenv creation 
 
+- refine determination if we run from Jenkins, thanks Borge Lanes.
+
 
 1.8.1
 -----------

Repository URL: https://bitbucket.org/hpk42/tox/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

From issues-reply at bitbucket.org  Fri Dec 12 06:44:16 2014
From: issues-reply at bitbucket.org (Michael Young)
Date: Fri, 12 Dec 2014 05:44:16 -0000
Subject: [Pytest-commit] Issue #643: Show number of assertions in test
	results (hpk42/pytest)
Message-ID: <20141212054416.8997.59413@app10.ash-private.bitbucket.org>

New issue 643: Show number of assertions in test results
https://bitbucket.org/hpk42/pytest/issue/643/show-number-of-assertions-in-test-results

Michael Young:

In addition to the number of test cases run, it would be great to see the number of assertions.



From issues-reply at bitbucket.org  Sun Dec 14 00:13:55 2014
From: issues-reply at bitbucket.org (Henry Kupty)
Date: Sat, 13 Dec 2014 23:13:55 -0000
Subject: [Pytest-commit] Issue #644: Asyncio Loop gets closed (hpk42/pytest)
Message-ID: <20141213231355.21188.90197@app09.ash-private.bitbucket.org>

New issue 644: Asyncio Loop gets closed
https://bitbucket.org/hpk42/pytest/issue/644/asyncio-loop-gets-closed

Henry Kupty:

I'm writing a software with python's asyncio event lib and got an error while testing the async method.





From issues-reply at bitbucket.org  Tue Dec 16 17:59:58 2014
From: issues-reply at bitbucket.org (Steffen Roecker)
Date: Tue, 16 Dec 2014 16:59:58 -0000
Subject: [Pytest-commit] Issue #645: pytest.raises(AssertionError) fails
 with compiled cython modules (hpk42/pytest)
Message-ID: <20141216165958.10400.51865@app07.ash-private.bitbucket.org>

New issue 645: pytest.raises(AssertionError) fails with compiled cython modules
https://bitbucket.org/hpk42/pytest/issue/645/pytestraises-assertionerror-fails-with

Steffen Roecker:

This issue seems similar to issue #176.
Running with unittest works fine, however pytest fails when the imported module assert_helper is compiled to a .so with Cython.

cython assert_helper.py
gcc -c -fPIC -I/usr/include/python2.5/ assert_helper.c
gcc -shared assert_helper.o -o assert_helper.so

platform linux2 -- Python 2.7.3 -- py-1.4.26 -- pytest-2.6.4
plugins: xdist, cov, mock
Cython==0.21



From issues-reply at bitbucket.org  Wed Dec 17 15:05:22 2014
From: issues-reply at bitbucket.org (JocelynDelalande)
Date: Wed, 17 Dec 2014 14:05:22 -0000
Subject: [Pytest-commit] Issue #646: AttributeError: 'module' object has no
 attribute 'makegateway' (hpk42/pytest)
Message-ID: <20141217140522.19655.66452@app02.ash-private.bitbucket.org>

New issue 646: AttributeError: 'module' object has no attribute 'makegateway'
https://bitbucket.org/hpk42/pytest/issue/646/attributeerror-module-object-has-no

JocelynDelalande:

Just pip installed pytest-xdist

If I run it with "-f", I get: 

```
Traceback (most recent call last):
  File "/home/jocelyn/.virtualenvs/munch/bin/py.test", line 9, in <module>
    load_entry_point('pytest==2.6.1', 'console_scripts', 'py.test')()
  File "/home/jocelyn/.virtualenvs/munch/lib/python3.2/site-packages/_pytest/config.py", line 41, in main
    return config.hook.pytest_cmdline_main(config=config)
  File "/home/jocelyn/.virtualenvs/munch/lib/python3.2/site-packages/_pytest/core.py", line 413, in __call__
    return self._docall(methods, kwargs)
  File "/home/jocelyn/.virtualenvs/munch/lib/python3.2/site-packages/_pytest/core.py", line 424, in _docall
    res = mc.execute()
  File "/home/jocelyn/.virtualenvs/munch/lib/python3.2/site-packages/_pytest/core.py", line 315, in execute
    res = method(**kwargs)
  File "/home/jocelyn/.virtualenvs/munch/lib/python3.2/site-packages/xdist/plugin.py", line 58, in pytest_cmdline_main
    looponfail_main(config)
  File "/home/jocelyn/.virtualenvs/munch/lib/python3.2/site-packages/xdist/looponfail.py", line 20, in looponfail_main
    remotecontrol.loop_once()
  File "/home/jocelyn/.virtualenvs/munch/lib/python3.2/site-packages/xdist/looponfail.py", line 85, in loop_once
    self.setup()
  File "/home/jocelyn/.virtualenvs/munch/lib/python3.2/site-packages/xdist/looponfail.py", line 49, in setup
    self.gateway = self.initgateway()
  File "/home/jocelyn/.virtualenvs/munch/lib/python3.2/site-packages/xdist/looponfail.py", line 41, in initgateway
    return execnet.makegateway("popen")
AttributeError: 'module' object has no attribute 'makegateway'
```

Relevant packages versions :
```
#!
pytest==2.6.1
pytest-django==2.7.0
pytest-xdist==1.11
```

Using python 3.2



From issues-reply at bitbucket.org  Thu Dec 18 01:38:11 2014
From: issues-reply at bitbucket.org (Tony Tan)
Date: Thu, 18 Dec 2014 00:38:11 -0000
Subject: [Pytest-commit] Issue #202: Tox cannot install nose/sphinx
 dependency on Mac OS (hpk42/tox)
Message-ID: <20141218003811.1026.79952@app14.ash-private.bitbucket.org>

New issue 202: Tox cannot install nose/sphinx dependency on Mac OS
https://bitbucket.org/hpk42/tox/issue/202/tox-cannot-install-nose-sphinx-dependency

Tony Tan:

When I tried to run tox in a py34 environment, tox errors out with a failure to install nose (if sphinx is in dependency it will end up with the same problem), seems like 2to3 messed up somehow in tox:


```
#!python

Fixing build/lib/nose/__init__.py build/lib/nose/__main__.py build/lib/nose/case.py build/lib/nose/commands.py build/lib/nose/config.py build/lib/nose/core.py build/lib/nose/exc.py build/lib/nose/failure.py build/lib/nose/importer.py build/lib/nose/inspector.py build/lib/nose/loader.py build/lib/nose/proxy.py build/lib/nose/pyversion.py build/lib/nose/result.py build/lib/nose/selector.py build/lib/nose/suite.py build/lib/nose/twistedtools.py build/lib/nose/util.py build/lib/nose/ext/__init__.py build/lib/nose/ext/dtcompat.py build/lib/nose/plugins/__init__.py build/lib/nose/plugins/allmodules.py build/lib/nose/plugins/attrib.py build/lib/nose/plugins/base.py build/lib/nose/plugins/builtin.py build/lib/nose/plugins/capture.py build/lib/nose/plugins/collect.py build/lib/nose/plugins/cover.py build/lib/nose/plugins/debug.py build/lib/nose/plugins/deprecated.py build/lib/nose/plugins/doctests.py build/lib/nose/plugins/errorclass.py build/lib/nose/plugins/failuredetail.py build/li
 b/nose/plugins/isolate.py build/lib/nose/plugins/logcapture.py build/lib/nose/plugins/manager.py build/lib/nose/plugins/multiprocess.py build/lib/nose/plugins/plugintest.py build/lib/nose/plugins/prof.py build/lib/nose/plugins/skip.py build/lib/nose/plugins/testid.py build/lib/nose/plugins/xunit.py build/lib/nose/sphinx/__init__.py build/lib/nose/sphinx/pluginopts.py build/lib/nose/tools/__init__.py build/lib/nose/tools/nontrivial.py build/lib/nose/tools/trivial.py
    Skipping implicit fixer: buffer
    Skipping implicit fixer: idioms
    Skipping implicit fixer: set_literal
    Skipping implicit fixer: ws_comma
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/Users/tony7514/projects/Rackspace/cdn/.tox/py34/build/nose/setup.py", line 123, in <module>
        **addl_args
      File "/Users/tony7514/projects/Rackspace/cdn/.tox/py34/build/nose/setup3lib.py", line 140, in setup
        return _setup(*args, **kwargs)
      File "/usr/local/Cellar/python3/3.4.1_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/core.py", line 148, in setup
        dist.run_commands()
      File "/usr/local/Cellar/python3/3.4.1_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 955, in run_commands
        self.run_command(cmd)
      File "/usr/local/Cellar/python3/3.4.1_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 974, in run_command
        cmd_obj.run()
      File "/Users/tony7514/projects/Rackspace/cdn/.tox/py34/lib/python3.4/site-packages/setuptools/command/install.py", line 59, in run
        return orig.install.run(self)
      File "/usr/local/Cellar/python3/3.4.1_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/command/install.py", line 566, in run
        self.run_command(cmd_name)
      File "/usr/local/Cellar/python3/3.4.1_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/usr/local/Cellar/python3/3.4.1_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 974, in run_command
        cmd_obj.run()
      File "/Users/tony7514/projects/Rackspace/cdn/.tox/py34/lib/python3.4/site-packages/setuptools/command/install_egg_info.py", line 29, in run
        self.run_command('egg_info')
      File "/usr/local/Cellar/python3/3.4.1_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/usr/local/Cellar/python3/3.4.1_1/Frameworks/Python.framework/Versions/3.4/lib/python3.4/distutils/dist.py", line 974, in run_command
        cmd_obj.run()
      File "/Users/tony7514/projects/Rackspace/cdn/.tox/py34/lib/python3.4/site-packages/setuptools/command/egg_info.py", line 155, in run
        writer = ep.load(installer=installer)
      File "/Users/tony7514/projects/Rackspace/cdn/.tox/py34/lib/python3.4/site-packages/pkg_resources.py", line 2147, in load
        ['__name__'])
      File "/Users/tony7514/projects/Rackspace/cdn/.tox/py34/lib/python3.4/site-packages/pbr/packaging.py", line 476, in <module>
        from nose import commands
      File "/Users/tony7514/projects/Rackspace/cdn/.tox/py34/build/nose/nose/__init__.py", line 1, in <module>
        from nose.core import collector, main, run, run_exit, runmodule
      File "/Users/tony7514/projects/Rackspace/cdn/.tox/py34/build/nose/nose/core.py", line 153
        print "%s version %s" % (os.path.basename(sys.argv[0]), __version__)
```

This is my tox.ini file:


```
#!ini

[tox]
minversion = 1.6
envlist = py26,py27,py33,py34,pypy,pep8
skipsdist = True

[testenv]
usedevelop = True
# Customize pip command, add -U to force updates.
install_command = pip install -U {opts} {packages}
setenv = VIRTUAL_ENV={envdir}
         NOSE_WITH_OPENSTACK=1
         NOSE_OPENSTACK_COLOR=1
         NOSE_OPENSTACK_RED=0.05
         NOSE_OPENSTACK_YELLOW=0.025
         NOSE_OPENSTACK_SHOW_ELAPSED=1
         NOSE_OPENSTACK_STDOUT=1
deps = -r{toxinidir}/requirements/requirements.txt
       -r{toxinidir}/tests/test-requirements.txt
commands = pip install git+https://github.com/stackforge/opencafe.git#egg=cafe
           pip install git+https://github.com/tonytan4ever/python-maxcdn.git#egg=maxcdn
           nosetests {posargs:--exclude=api --exclude=endtoend --nologcapture}

[tox:jenkins]
downloadcache = ~/cache/pip

[testenv:py33]
sitepackages=True

[testenv:py34]
#sitepackages=True

[testenv:pep8]
commands = flake8

[testenv:lint2]
basepython = python2
deps = {[testenv]deps}
       pylint
commands = pylint ./poppy
           pylint ./tests

[testenv:lint3]
basepython = python3
deps = {[testenv]deps}
       pylint
commands = pylint ./poppy
           pylint ./tests

[testenv:docs]
deps = -r{toxinidir}/requirements/requirements.txt
       -r{toxinidir}/tests/test-requirements.txt
commands = 
    python setup.py build_sphinx -E -a
    python setup.py build_sphinx -E -a -b doctest
    python setup.py build_sphinx -E -a -b coverage

[testenv:cover]
setenv = NOSE_WITH_COVERAGE=1

[testenv:venv]
commands = {posargs}

[flake8]
builtins = __CDN_SETUP__
exclude = .venv*,venv*,.git,.tox,dist,doc,*openstack/common*,*lib/python*,*.egg,.update-venv

[hacking]
import_exceptions = poppy.openstack.common.gettextutils._

[testenv:apidocker]
deps = -r{toxinidir}/requirements/requirements.txt
       -r{toxinidir}/tests/test-requirements.txt
whitelist_externals = docker
setenv = CAFE_CONFIG_FILE_PATH={homedir}/.poppy/tests.conf
         CAFE_ROOT_LOG_PATH={homedir}/.poppy/logs
         CAFE_TEST_LOG_PATH={homedir}/.poppy/logs

         NOSE_WITH_OPENSTACK=1
         NOSE_OPENSTACK_COLOR=1
         NOSE_OPENSTACK_RED=0.05
         NOSE_OPENSTACK_YELLOW=0.025
         NOSE_OPENSTACK_SHOW_ELAPSED=1
         NOSE_OPENSTACK_STDOUT=1

commands =
    pip install git+https://github.com/stackforge/opencafe.git#egg=cafe
    pip install -U fig

    {toxinidir}/docker/fig/dev -f fig_local.yml up -d
    nosetests api --nologcapture
```


Tried with system default py34 pip and , it can install nose successfully.



From issues-reply at bitbucket.org  Thu Dec 18 18:19:59 2014
From: issues-reply at bitbucket.org (Tom Bechtold)
Date: Thu, 18 Dec 2014 17:19:59 -0000
Subject: [Pytest-commit] Issue #203: tox failes when ":" is in the current
 directory path (hpk42/tox)
Message-ID: <20141218171959.31596.75607@app01.ash-private.bitbucket.org>

New issue 203: tox failes when ":" is in the current directory path
https://bitbucket.org/hpk42/tox/issue/203/tox-failes-when-is-in-the-current

Tom Bechtold:

This is on linux. Trying to execute tox when the path contains a ":" doesn't work:

```
$ pwd
/home/tom/devel/bla:blub/tox
tom at basilikum:~/devel/bla:blub/tox$ tox
GLOB sdist-make: /home/tom/devel/bla:blub/tox/setup.py
Traceback (most recent call last):
  File "/usr/bin/tox", line 9, in <module>
    load_entry_point('tox==1.7.2', 'console_scripts', 'tox-2.7')()
  File "/usr/lib/python2.7/site-packages/tox/_cmdline.py", line 26, in main
    retcode = Session(config).runcommand()
  File "/usr/lib/python2.7/site-packages/tox/_cmdline.py", line 310, in runcommand
    return self.subcommand_test()
  File "/usr/lib/python2.7/site-packages/tox/_cmdline.py", line 448, in subcommand_test
    if self.setupenv(venv):
  File "/usr/lib/python2.7/site-packages/tox/_cmdline.py", line 377, in setupenv
    envlog.set_python_info(commandpath)
  File "/usr/lib/python2.7/site-packages/tox/result.py", line 47, in set_python_info
    "import sys; "
  File "/usr/lib/python2.7/site-packages/py/_path/local.py", line 695, in sysexec
    stdout, stderr,)
py.process.cmdexec.Error: ExecutionFailed: 1  /home/tom/devel/bla:blub/tox/.tox/py27/bin/python
ImportError: No module named site
```

Moving the same code to another directory and executing tox works fine.



From commits-noreply at bitbucket.org  Sat Dec 20 21:42:16 2014
From: commits-noreply at bitbucket.org (commits-noreply at bitbucket.org)
Date: Sat, 20 Dec 2014 20:42:16 -0000
Subject: [Pytest-commit] commit/tox: aconrad: explain how to disable
	PYTHONHASHSEED
Message-ID: <20141220204216.3866.43283@app01.ash-private.bitbucket.org>

1 new commit in tox:

https://bitbucket.org/hpk42/tox/commits/50f3b98fc65b/
Changeset:   50f3b98fc65b
User:        aconrad
Date:        2014-12-20 00:54:58+00:00
Summary:     explain how to disable PYTHONHASHSEED
Affected #:  2 files

diff -r 7109f1184d9f0303b050fce006cd90fa3db9e26e -r 50f3b98fc65b951ab07e6b5e3fbd5a2fc9c48f2c CHANGELOG
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -95,7 +95,7 @@
   
 - merged PR125: tox now sets "PYTHONHASHSEED" to a random value
   and offers a "--hashseed" option to repeat a test run with a specific seed.
-  You can also use --hashsheed=notset to instruct tox to leave the value
+  You can also use --hashsheed=noset to instruct tox to leave the value
   alone.  Thanks Chris Jerdonek for all the work behind this.
 
 - fix issue132: removing zip_safe setting (so it defaults to false)

diff -r 7109f1184d9f0303b050fce006cd90fa3db9e26e -r 50f3b98fc65b951ab07e6b5e3fbd5a2fc9c48f2c doc/example/basic.txt
--- a/doc/example/basic.txt
+++ b/doc/example/basic.txt
@@ -191,10 +191,14 @@
 command-line option to ``tox``.  You can also override the hash seed value
 per test environment in ``tox.ini`` as follows::
 
-    [testenv:hash]
+    [testenv]
     setenv =
         PYTHONHASHSEED = 100
 
+If you wish to disable this feature, you can pass the command line option
+``--hashseed=noset`` when ``tox`` is invoked. You can also disable it from the
+``tox.ini`` by setting ``PYTHONHASHSEED = 0`` as described above.
+
 .. _`in Python 3.3`: http://docs.python.org/3/whatsnew/3.3.html#builtin-functions-and-types
 .. _PYTHONHASHSEED: http://docs.python.org/using/cmdline.html#envvar-PYTHONHASHSEED

Repository URL: https://bitbucket.org/hpk42/tox/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.

From issues-reply at bitbucket.org  Sun Dec 21 12:51:03 2014
From: issues-reply at bitbucket.org (vmalloc)
Date: Sun, 21 Dec 2014 11:51:03 -0000
Subject: [Pytest-commit] Issue #647: Automatically stop console output
 capturing when pudb is used (hpk42/pytest)
Message-ID: <20141221115103.12493.33151@app07.ash-private.bitbucket.org>

New issue 647: Automatically stop console output capturing when pudb is used
https://bitbucket.org/hpk42/pytest/issue/647/automatically-stop-console-output

vmalloc:

Currently py.test correctly identifies when pdb kicks in and temporarily stops output capturing. This also works for ipdb AFAIK. When trying to use pudb to debug or set_trace in running code, the output capturing is not turned off, thus causing an error. It would be nice for pudb to be recognized as well.



From issues-reply at bitbucket.org  Mon Dec 22 18:06:24 2014
From: issues-reply at bitbucket.org (Thomas Trenner)
Date: Mon, 22 Dec 2014 17:06:24 -0000
Subject: [Pytest-commit] Issue #648: Platform information in test session
 startup (hpk42/pytest)
Message-ID: <20141222170624.32409.43128@app13.ash-private.bitbucket.org>

New issue 648: Platform information in test session startup
https://bitbucket.org/hpk42/pytest/issue/648/platform-information-in-test-session

Thomas Trenner:

This is reporting 'win32' even when run with x64 Python. Pull request #236 opened for this.



From issues-reply at bitbucket.org  Thu Dec 25 18:43:53 2014
From: issues-reply at bitbucket.org (Ian Cordasco)
Date: Thu, 25 Dec 2014 17:43:53 -0000
Subject: [Pytest-commit] Issue #204: testrun.org's certificate expired on
	Nov 20 (hpk42/tox)
Message-ID: <20141225174353.14961.14380@app05.ash-private.bitbucket.org>

New issue 204: testrun.org's certificate expired on Nov 20
https://bitbucket.org/hpk42/tox/issue/204/testrunorgs-certificate-expired-on-nov-20

Ian Cordasco:

Please create/purchase a new certificate



From issues-reply at bitbucket.org  Fri Dec 26 11:58:41 2014
From: issues-reply at bitbucket.org (Fredrik Blomqvist)
Date: Fri, 26 Dec 2014 10:58:41 -0000
Subject: [Pytest-commit] Issue #205: {envname} substitution does not exist
	(hpk42/tox)
Message-ID: <20141226105841.20890.28760@app05.ash-private.bitbucket.org>

New issue 205: {envname} substitution does not exist
https://bitbucket.org/hpk42/tox/issue/205/envname-substitution-does-not-exist

Fredrik Blomqvist:

I tried using it in the following config:


```
#!python

[tox]
envlist = py27, py32, py33, py34

[testenv]
commands = {envpython} setup.py test
envdir = {homedir}/.virtualenvs/projectname-{envname}
```

I get this error:

```
#!

tox.ConfigError: ConfigError: substitution key 'envname' not found
```



From issues-reply at bitbucket.org  Mon Dec 29 15:11:06 2014
From: issues-reply at bitbucket.org (Alfredo Deza)
Date: Mon, 29 Dec 2014 14:11:06 -0000
Subject: [Pytest-commit] Issue #649: parametrized test nodes cannot be
 specified to run on the command line (hpk42/pytest)
Message-ID: <20141229141106.25546.59579@app14.ash-private.bitbucket.org>

New issue 649: parametrized test nodes cannot be specified to run on the command line
https://bitbucket.org/hpk42/pytest/issue/649/parametrized-test-nodes-cannot-be

Alfredo Deza:

If a file called `test_foo.py` has a `test_add` function, the normal notation to call that specific function on the command line is:


```
py.test /path/to/test_foo::test_add
```

But if the function is parametrized the node ids change (seen with high verbosity and `--collect-only`) at runtime, so it makes it impossible to specify any parametrized test to run unless one just points to the whole file (as opposed to a single test node)

It would be nice if there was a way to specify such parametrized test nodes to run. Currently the behavior is that py.test will error with:


```
#!

(tmp)papaya-2 ~/tmp ? py.test -vvv "/Users/alfredo/tmp/test_fail.py::test_adding"
============================== test session starts ==============================
platform darwin -- Python 2.7.5 -- py-1.4.20 -- pytest-2.5.2 -- /Users/alfredo/.virtualenvs/tmp/bin/python
collecting 3 itemsERROR: not found: /Users/alfredo/tmp/test_fail.py::test_adding
(no name '/Users/alfredo/tmp/test_fail.py::test_adding' in any of [<Module 'test_fail.py'>])

===============================  in 0.01 seconds ================================
```

The contents of the test is:


```
#!

(tmp)papaya-2 ~/tmp ? cat test_fail.py
import pytest


@pytest.mark.parametrize(('inp', 'expected'),
[
    ('2 + 2', 4),
    ('0 + 0', 0),
    ('2 + 2.0', 4.0),
])
def test_adding(inp, expected):
    assert eval(inp) == expected
```

This affects `pytest.vim` as it relies heavily on this particular feature so that a user can run specific tests from Vim.

pytest.vim related issue: https://github.com/alfredodeza/pytest.vim/issues/23



From issues-reply at bitbucket.org  Wed Dec 31 18:16:32 2014
From: issues-reply at bitbucket.org (chriswwolfe)
Date: Wed, 31 Dec 2014 17:16:32 -0000
Subject: [Pytest-commit] Issue #206: Add platform name tag to config options
	(hpk42/tox)
Message-ID: <20141231171632.3471.53308@app02.ash-private.bitbucket.org>

New issue 206: Add platform name tag to config options
https://bitbucket.org/hpk42/tox/issue/206/add-platform-name-tag-to-config-options

chriswwolfe:

It would be helpful if one could specify the platform on which a test environment should be executed. This would function in a manner similar to the python version tag.

I'm proposing this to address the following pain point: I'm building an application that will be run on linux and osx. I'm also building a bundled version of the application with py2app and pyobjc. Ideally, I'd like to have a tox env that is only run when the platform is osx.

The syntax I propose is

[testenv:bundle]
platforms = osx, linux

Here is a copy of the IRC log in which the issue was discussed (I pasted it as gist for formatting): https://gist.github.com/derwolfe/0f548b0dbfabbb89f5e1




From issues-reply at bitbucket.org  Wed Dec 31 21:00:25 2014
From: issues-reply at bitbucket.org (Charles Cloud)
Date: Wed, 31 Dec 2014 20:00:25 -0000
Subject: [Pytest-commit] Issue #650: Allow --doctest-modules to skip modules
 on ImportError (hpk42/pytest)
Message-ID: <20141231200025.2679.10573@app03.ash-private.bitbucket.org>

New issue 650: Allow --doctest-modules to skip modules on ImportError
https://bitbucket.org/hpk42/pytest/issue/650/allow-doctest-modules-to-skip-modules-on

Charles Cloud:

We're working on a library that has many optional dependencies but we also find doctests to be a very effective way to illustrate simple examples of functions and test them at the same time. We'd be overjoyed if there was a way in `py.test` to have an option that allows us to skip doctesting files that have things that cannot be imported.

Something like:

`--doctest-skip-on-import-failure` (maybe something less verbose, but we'd be happy either way)

I'm also happy to close the issue if there's already a way to do this. Thanks!