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

Move to Python 3 #6

Open
vikhari opened this issue Sep 5, 2018 · 1 comment
Open

Move to Python 3 #6

vikhari opened this issue Sep 5, 2018 · 1 comment
Assignees
Labels
Project-Improvement Feature needs specific improvement.

Comments

@vikhari
Copy link
Member

vikhari commented Sep 5, 2018

Python 2 was used for Ontospy and other tools. If Python 3 can be used for Autogeneration and the API itself, etc. then we should transition. This should likely be done after reaching a stable version of CASE to first get the workflow and framework more stable.

@vikhari vikhari added the Project-Improvement Feature needs specific improvement. label Sep 5, 2018
@vikhari vikhari self-assigned this Sep 5, 2018
@vikhari
Copy link
Member Author

vikhari commented Sep 5, 2018

Python 3 may be able to use other (simpler) ways to type check, possibly dynamically, which could be used to change the API. I have not looked into these yet, but here are some links for future reference:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Project-Improvement Feature needs specific improvement.
Projects
None yet
Development

No branches or pull requests

1 participant