Skip to content
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

PySys_SetPath must go after Py_Initialize #410

Merged
merged 1 commit into from Aug 20, 2013

Conversation

theY4Kman
Copy link
Contributor

I believe (but have not confirmed) it is because PySys_SetPath calls PySys_SetObject, which retrieves the sysdict from the Python thread state, which is not initialized until Py_Initialize. Cheers!

I believe (but have not confirmed) it is because PySys_SetPath calls PySys_SetObject, which retrieves the sysdict from the Python thread state, which is not initialized until Py_Initialize. Cheers!
arr2036 added a commit that referenced this pull request Aug 20, 2013
PySys_SetPath must go after Py_Initialize
@arr2036 arr2036 merged commit 7e69d9f into FreeRADIUS:master Aug 20, 2013
@arr2036
Copy link
Member

arr2036 commented Aug 20, 2013

If you can reproduce and fix #408 you get all the internet points.

@theY4Kman
Copy link
Contributor Author

Ooh, I missed your comment, but challenge accepted.

@theY4Kman
Copy link
Contributor Author

Or never mind :P

@arr2036
Copy link
Member

arr2036 commented Dec 15, 2013

Never did figure out the actual issue, just set the module to be single threaded. Looks like the TLS stuff isn't working properly and new interpreters aren't being created. If you have time all the internet points are still yours :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants