-
-
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
Move py.code to pytest.code #103
Comments
this is mostly a code+test copy followed by adjustments, ask me on irc for details |
After poking around in py.code during the PyConUK sprint, I'm going to take a look at making this move. |
its rather tricky, i treif before but abadonded due to py.code having a lot of interaction via py.code usage internally - be carefull |
WIP, some tests still fail. Tests also need moving across.
I've made an attempt of this at master...Bjwebb:issue-103-move-py-code This now successfully runs the test suite on Python2.7 and 3.4, but there are still flakes errors - https://travis-ci.org/Bjwebb/pytest/builds/81460589 In order to get |
there should be no pytest.code for now, its preferable that we have _pytest.code for now as a internal API thats allowed to change |
@Bjwebb any news on this? Would you mind opening a PR targeting |
This is dependent on a feature branch of the py repository Fix pytest-dev#103 test_assertion passed Add code Add code All code tests passing All tests passing Add _pytest.code to list of packages Fix flakes
This is dependent on a feature branch of the py repository Fix pytest-dev#103
fixed by the pr |
Originally reported by: holger krekel (BitBucket: hpk42, GitHub: hpk42)
Often fixes to pytest actually need to happen in the pylib, namely py.code. Moreover, there probably are very few uses of the py.code.* API outside of pytest and pypy. Therefore i think it makes sense to remove the dependency of pytest on py.code and move the namespace to pytest.code.
The text was updated successfully, but these errors were encountered: