-
-
Notifications
You must be signed in to change notification settings - Fork 531
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
Add {envsitedir} substitution. #72
Comments
Original comment by @tkf How about |
Original comment by @hpk42 I think we deifnitely need recommendations how to deal with 2to3. Not sure i get to it in the next weeks. Using "envsitepackagesdir" is kind of a hack, it should be possible to have things working more easily. Haven't thought in depth about it yet, though. |
Original comment by @g2p Ah, and without 2to3, this snippet also prevents py.test reporting an import file mismatch between the build/ directory (which pytest tried to collect) and the vcs version (which ends up imported). |
Original comment by @g2p
|
Original comment by @g2p py.test finds the non-2to3 source from the vcs checkout in both cases. |
Original comment by @hpk42 in which case does the normal "--cov=mypkg" not work? And what happens, if you do do "py.test --cov=mypkg --pyargs mypkg" btw? |
Original comment by @g2p I have this snippet that works reliably in the presence of 2to3 (edit: the multiprocessing thing was a red herring), should I mention it in one of the examples?
|
Original comment by @g2p |
It seems tricky to figure out the site-packages dir from outside the virtualenv (distutils.sysconfig is inadequate if the interpreter version changes), but it would make certain hacks to get file-based test runners to cooperate with 2to3 much easier.
The text was updated successfully, but these errors were encountered: