FazBrowse GitHub Viewer
|
Trending
|
URL:
|
Home
Tools:
[Download Repo ZIP]
[Original HTTPS Page]
Fix _at_fork_reinit to write INIT directly instead of calling unlock() by youknowone · Pull Request #7312 · RustPython/RustPython · GitHub
Uh oh!
There was an error while loading.
Please reload this page
.
RustPython
/
RustPython
Public
Notifications
You must be signed in to change notification settings
Fork
1.5k
Star
22.3k
Code
Issues
295
Pull requests
100
Discussions
Actions
Projects
Wiki
Security and quality
0
Insights
Additional navigation options
Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security and quality
Insights
Fix _at_fork_reinit to write INIT directly instead of calling unlock()
- #7312
#7312
Merged
youknowone
merged 2 commits into
RustPython:main
RustPython/RustPython:main
from
youknowone:fork-reinit
youknowone/RustPython:fork-reinit
Copy head branch name to clipboard
Mar 3, 2026
Conversation
Commits
2
(2)
Checks
Files changed
Merged
Fix _at_fork_reinit to write INIT directly instead of calling unlock()
#7312
youknowone
merged 2 commits into
RustPython:main
RustPython/RustPython:main
from
youknowone:fork-reinit
youknowone/RustPython:fork-reinit
Copy head branch name to clipboard
Commits
Commits on Mar 2, 2026
Fix _at_fork_reinit to write INIT directly instead of calling unlock()
Show description for f00fcd2
youknowone
committed
f00fcd2
View commit details
Copy full SHA for f00fcd2
Browse repository at this point
Add import lock (IMP_LOCK) reinit after fork
Show description for 2893430
youknowone
committed
2893430
View commit details
Copy full SHA for 2893430
Browse repository at this point
Back
|
FazBrowse Home
|
New Git URL