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

Issues with Python 3.4 #25

Closed
sjlnk opened this issue Aug 4, 2014 · 4 comments
Closed

Issues with Python 3.4 #25

sjlnk opened this issue Aug 4, 2014 · 4 comments

Comments

@sjlnk
Copy link

sjlnk commented Aug 4, 2014

Swigibpy has some minor issues with Python 3.4. Fixing it was quite easy, just replacing all instances of dict.iteritems() with dict.items() in swigibpy.py solved the problem. Will keep an eye out for other incompatibilities and report them here...

Can this fix be merged in the repository?

@Komnomnomnom
Copy link
Owner

Thanks @azyr that's great :-). Would you mind submitting a pull request with the changes you mentioned and any other incompatibilities you find?

@sjlnk
Copy link
Author

sjlnk commented Aug 4, 2014

@Komnomnomnom I will do this a bit later.

I just bumped into a weird problem that I didn't have before when using Python 3.3. Whenever an exception gets raised (from my erroneous code) it somehow gets caught and I only get some useless output on EWrapper.Error. The output comes with code 509 and says: "Exception caught while reading socket - std::exception". This is very annoying because now I have no idea what I did wrong. Any ideas how can I raise the exceptions unhandled so I will know exactly what is going on?

@Komnomnomnom
Copy link
Owner

Thanks @azyr I'll look into it. Opened issue #26 to track this separately

@Komnomnomnom
Copy link
Owner

Fixed by c142d2f

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

No branches or pull requests

2 participants