-
-
Notifications
You must be signed in to change notification settings - Fork 907
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
setup.py test
fails with Python 3.6: AttributeError: module 'S3.Progress' has no attribute 'ProgressCR'
#996
Comments
The reason for the failure seems to be that Python's unittest module imports each and every module it can find in order to find tests by name (see
If on the other hand,
|
Adding Unfortunately,
|
Having imports right for python3 is very tricky when we have multiple way to use a command/lib. But I don't understand what you are trying to achieve, just don't use "setup.py test", If you want to perform some self test on s3cmd, there are 2 run_tests.py scripts dedicated to do that. It involves running a self contained server binary "minio" to act as a server. |
Yes, I understand that not running the non-existing tests is a solution. Nevertheless, it wasn't easy for me to decide if In my opinion When I get the output from Python 2.7 ( Each and every (Linux) distribution has to double check this, when packaging Feel free to close this issue. Also, thank you for writing and maintaining |
Fixed in MASTER now. |
python3.6 -B setup.py test
fails. I haven't checked other Python 3 versions. The error is as follows.AttributeError: module 'S3.Progress' has no attribute 'ProgressCR'
I understand that no tests are run by
setup.py
. We are building s3cmd and executing tests in an automated way. We are currently working around this by disabling the tests. It would be nice if the problem can still be fixed.The tests don't fail with Python 2.7.
As far as I can see the problem is due to a circular dependency:
S3/Progress.py
->S3/Utils.py
->S3/Config.py
->S3/Progress.py
.Here is the full output.
Is I said, the steps don't fail with Python 2.7.
The text was updated successfully, but these errors were encountered: