-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
document disabling byte-code writing via conftest #1680
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
Comments
Hey Ronny, in which situations one would get stale |
delete a module, have a pyc around, imports wont fail |
Ohhh I see, thanks. Couldn't the user just call that at the top of the root contest file? |
experimenting with that now, we might want to document it |
@RonnyPfannschmidt I would be interested in doing this. Do we want to implement this as a |
it should be documented for use with conftest |
Also changed how the section is presented: instead of "Note" blocks, use proper sections as those contain enough information to exist on their own. Fix pytest-dev#1680
Also changed how the section is presented: instead of "Note" blocks, use proper sections as those contain enough information to exist on their own. Fix pytest-dev#1680
when developing projects that are subject to change,
its easy to forget to remove stale pyc files,
thus i propose adding a ini option that sets sys.dont_write_bytecode before importing the first conftest
The text was updated successfully, but these errors were encountered: