-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
remove pytest internal usage of the namespace hook #2315
Merged
nicoddemus
merged 25 commits into
pytest-dev:features
from
RonnyPfannschmidt:namespace-hook
Apr 21, 2017
Merged
remove pytest internal usage of the namespace hook #2315
nicoddemus
merged 25 commits into
pytest-dev:features
from
RonnyPfannschmidt:namespace-hook
Apr 21, 2017
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RonnyPfannschmidt
changed the title
remove pytest internal usage of the namespace hoolk
remove pytest internal usage of the namespace hook
Mar 20, 2017
RonnyPfannschmidt
force-pushed
the
namespace-hook
branch
from
March 20, 2017 14:48
21c2dcf
to
22cb978
Compare
the xdist failure is most interesting |
#2321 could be considered a blocker, a decission is needed |
the xfail is probably a bad idea, for now i do not want to merge it, its no longer sane to try this for 3.1 |
RonnyPfannschmidt
changed the title
remove pytest internal usage of the namespace hook
[wip] remove pytest internal usage of the namespace hook
Mar 20, 2017
RonnyPfannschmidt
force-pushed
the
namespace-hook
branch
from
March 28, 2017 08:28
434ca5c
to
8ac6231
Compare
… builtin namespaces
RonnyPfannschmidt
force-pushed
the
namespace-hook
branch
from
March 28, 2017 09:45
8ac6231
to
afb1778
Compare
RonnyPfannschmidt
changed the title
[wip] remove pytest internal usage of the namespace hook
remove pytest internal usage of the namespace hook
Mar 29, 2017
nicoddemus
approved these changes
Apr 21, 2017
Hmm sorry, just now I saw your comment @RonnyPfannschmidt... should I revert this merge? |
Its fine, i dir put in a workaround that works by kerping a single hook in pytest |
blueyed
added a commit
to blueyed/pytest
that referenced
this pull request
Feb 24, 2020
Make it a real module instead. This was initially added in 9b58d6e (pytest-dev#2315), when removing support for `pytest_namespace`. Not sure if it ever worked "properly", but currently `import pytest.collect` and `from pytest.collect import File` do not work (but with this patch). This is only relevant for (backward) compatibility, but the more it appears to make sense to move it into a lazily loaded, separate file.
blueyed
added a commit
to blueyed/pytest
that referenced
this pull request
Mar 11, 2020
Make it a real module instead. This was initially added in 9b58d6e (pytest-dev#2315), when removing support for `pytest_namespace`. Not sure if it ever worked "properly", but currently `import pytest.collect` and `from pytest.collect import File` do not work (but with this patch). This is only relevant for (backward) compatibility, but the more it appears to make sense to move it into a lazily loaded, separate file.
blueyed
added a commit
to blueyed/pytest
that referenced
this pull request
Mar 12, 2020
Make it a real module instead. This was initially added in 9b58d6e (pytest-dev#2315), when removing support for `pytest_namespace`. Not sure if it ever worked "properly", but currently `import pytest.collect` and `from pytest.collect import File` do not work (but with this patch). This is only relevant for (backward) compatibility, but the more it appears to make sense to move it into a lazily loaded, separate file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
reopening of the prior pr #2280