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

Requires Python2.7 #3

Closed
rfinkers opened this issue Dec 5, 2017 · 4 comments
Closed

Requires Python2.7 #3

rfinkers opened this issue Dec 5, 2017 · 4 comments

Comments

@rfinkers
Copy link

rfinkers commented Dec 5, 2017

Dependency on "import option_parsers" in line 3 of tomba, which is not available anymore in python 3.

@wdecoster
Copy link

I don't believe there is a good enough reason to start a new project exclusively for Python2.7, aren't there alternatives for "option_parsers"?

@rfinkers
Copy link
Author

rfinkers commented Dec 5, 2017

No, I do not propose this and it is actually the opposite. It seems this code requires python 2.7 and does not work with python 3.0. If that is true, than it is a suggestion for the documentation.

@marcus1487
Copy link
Collaborator

Yes, this should be in the documentation. I will add a note in the documentation for this shortly.

For the "option_parsers" point, this is actually in internal module within the tombo framework. So that is simply the first item hit which does not compute in python3. Tombo is derived from the nanoraw framework and so the code base is about 2 years old now. There is a decent amount of work to convert tombo to a python3 framework, so this is not on the immediate todo list for tombo at this time.

marcus1487 added a commit that referenced this issue Dec 7, 2017
…bo documentation along with notes on issues brought up by users. Fixes #1, #2 and #3.
@marcus1487
Copy link
Collaborator

Fixed in 03d39b6

marcus1487 added a commit that referenced this issue Mar 2, 2021
…. Fisrt real working version of model re-squiggle. Still needs to be tested and seems to be very computationally intensive as well as leaky with memory, so defintely not completely ready. Initially fixes #3.
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

3 participants