New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AttributeError: test command fails with NoneType object has no attribute 'run' #183
Comments
Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco): Arfrever suggested this patch which almost surely would work, but it would mask the purpose of the code. Especially when supporting cross-python compatibility, I would prefer to have a wrapped to capture the compatibility logic (and thus describe when the compatibility logic is safe to remove, in this case after Python 2.6/3.1 is dropped). |
Original comment by arfrever (Bitbucket: arfrever, GitHub: arfrever): (I mentioned only Python 3.1 on IRC.) Content of my patch for historical reference:
|
Original comment by arfrever (Bitbucket: arfrever, GitHub: arfrever): 369f6f90f696 does not work:
|
Original comment by marcio_ (Bitbucket: marcio_, GitHub: Unknown): It appears this doesn't fix the same problem for Python 2.6. It also needs to translate testRunner==None to TextTestRunner.
|
Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco): @marciof If I trust the comments above (and I don't fully), the Travis-CI tests demonstrate that the commands run fine on Python 2.6. Of course, since then, the test runner has been converted to pytest, so it may no longer be the case that the invocation of setup.py test under Python 2.6 exercises the code in question. Still, at the time, apparently the tests were running under Python 2.6. Is it possible that the functionality was released in a patch version of Python 2.6 or that you're running a pre-release version of Python 2.6? What (full) version of Python 2.6 do you have? |
Original comment by marcio_ (Bitbucket: marcio_, GitHub: Unknown): Python 2.6 (r26:66721, Oct 2 2008, 11:35:03) [MSC v.1500 32 bit (Intel)] on win32. This is on Windows 8.1 32-bit with setuptools 18.2. I previously didn't have this problem for my hobby project, and it only appeared after upgrading setuptools, Windows and reinstalling Python 2.6 on a new PC (I don't remember the previous exact versions). I want to test this same combination on Linux, but I currently don't have easy access to do that. |
Remove CVS and Subversion references in include_package_data docs
Replace bespoke logging facility with logging module
Originally reported by: jaraco (Bitbucket: jaraco, GitHub: jaraco)
@Arfrever reports that the recent change to support custom test loaders (d9932598b86f) now causes AttributeErrors when no testLoader is supplied on Python 2.6 and 3.1.
The text was updated successfully, but these errors were encountered: