Work-around for Issue #120, xmlsec.initialize #149
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running the python-saml code in a stand-alone django development server everything works. As soon as I used the same code in a server environment, the python-saml code would fail in a similar fashion to ticket #120 . Both were Ubuntu machines running a current version (same python version) and both had the same libraries installed using apt and both were running the same python libraries in virtual environments.
I made changes to the python-saml code that limit initialization to the utils module and importing xmlsec from utils in other modules so that utils is the only place where xmlsec is initialized. I notice that there are updates to the thread since I made these changes so maybe another solution is in the works? My code is currently working.