no-op for un-evaluatable items in globals #25
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request carries out what was suggested in the email:
https://mail.python.org/pipermail/python-ldap/2016q3/003789.html
The project that I am working on has had to keep the version of pytest pinned ever since encountering the problem mentioned here, because pytest puts decorators in the pattern of
@something
as a key that shows up inside ofdir()
. A major takeaway is that you should not count on keys inside ofdir()
to be something that can be evaluated in all environments.https://github.com/ansible/awx/blob/devel/requirements/requirements_dev.txt#L8
If you could make this change, no existing workflow should be affected, and we will be able to upgrade pytest as soon as a new release of pytest-ldap is cut.
My alternative solution is that this diff would also suffice:
By the way, thank you for taking over management of this project. No one responded to my email, but I am delighted to be able to make the pull request directly now.