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

Work-around for Issue #120, xmlsec.initialize #149

Merged
merged 7 commits into from
Jul 19, 2016

Conversation

coolbootscoder
Copy link
Contributor

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.

@pitbulk
Copy link
Contributor

pitbulk commented Jul 2, 2016

Can you solve the pep8 issues?

@coolbootscoder
Copy link
Contributor Author

I'll work on that. I haven't read PEP8. I do most of my coding in an environment that keeps track of style, but I used the github editor for this code.

Added a new line for PIP8 requirement.
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.

2 participants