-
Notifications
You must be signed in to change notification settings - Fork 24
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
update porting guide #96
update porting guide #96
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! This is a much needed explanation of thread-safety issues around testing.
I left a few copy-editing comments.
docs/porting.md
Outdated
thread-safe, please do not open issues asking to fix thread safety issues in | ||
PyTest itself. | ||
|
||
#### The `warnings` module is not thread safe |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably be consistent in using either thread safe
or thread-safe
. No preference on my side.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ended up going with "thread-safe" and "thread safety", which follows wikipedia's style.
cb1f819
to
ae17365
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @ngoldbaum!
Fixes #92.
Ping @ogrisel.
I added discussion about working with thread-unsafe tests and expanded the discussion about
PyMutex
and the critical section API to discuss the interaction with the GIL.Also re-organized a little bit and changed the ToC hierarchy to make it flow better IMO.