update/adjustment of notebooks to Python 3 #65
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Again, the notebook was still expecting legacy Python-2.
Kernel and syntax already were in Python3. Works good.
Change of the anticipated kernel; syntax already was compatible with Python 3.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Running Linux Debian 12/bookworm (branch testing), I found some of the
notebooks still anticipating legacy Python 2; e.g., using
printas astatement instead as a function, or anticipating an old Python 2
kernel.
All four notebooks were checked; where necessary, adjusted. They work
fine within Jupyter (version 6.4.5) backed by Python (version 3.9.9).