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

Investigate python 3 compatibility #2

Closed
mperrin opened this issue Jun 25, 2012 · 2 comments
Closed

Investigate python 3 compatibility #2

mperrin opened this issue Jun 25, 2012 · 2 comments
Assignees

Comments

@mperrin
Copy link
Owner

mperrin commented Jun 25, 2012

Has not even been attempted yet. On the other hand, there is no clear statement of demand for python 3 webbpsf yet.

mperrin pushed a commit that referenced this issue May 19, 2014
Fix package init to not import py.test
@mperrin
Copy link
Owner Author

mperrin commented Nov 20, 2014

@cslocum Is there a standard SSB policy on Python 3 compatibility yet? Is this something we should prioritize or we're OK leaving aside for now?

If it's something that's worth pursuing actively, do you think it's something you might be able to help with? I presume there are some experts in SSB on writing 2/3 compatible code bases, and I see there are various helper libraries used for that purpose in astropy, but I don't have any firsthand experience of trying to develop on Python 3.

@mperrin
Copy link
Owner Author

mperrin commented Apr 12, 2015

Following @josePhoenix's success in getting poppy working on python 3 using 2to3 and six (mperrin/poppy#86) it was pleasantly straightforward to do the same for webbpsf. All tests pass on Python 3.4 now locally, though it looks like the Travis setup needs some tweaking to get them running there too.

josePhoenix pushed a commit to josePhoenix/webbpsf that referenced this issue Sep 7, 2016
mperrin pushed a commit that referenced this issue Jun 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants