Adding python 3.10 support#16
Merged
Merged
Conversation
CodeByDrescher
force-pushed
the
add_python_310
branch
from
83fc510 to
2796e6f
Compare
CodeByDrescher
force-pushed
the
add_python_310
branch
5 times, most recently
from
bae5b3c to
cee2ec2
Compare
CodeByDrescher
force-pushed
the
add_python_310
branch
from
cee2ec2 to
087df94
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Quick fix to solve issues with dependency installation in the pyvcell pipeline.
What this does
Reconciles
mainwith work already published to PyPI but never merged back:0.0.15.2→0.0.15.4Release reconciliation
These commits are the source of two existing tags/releases that
mainwas missing:0.0.15.32796e6f(adding python 3.10 support)0.0.15.44d0fdda(version bump — branch tip)mainwas at0.0.15.2while PyPI already had0.0.15.4; this bringsmainback in sync with what's published.Please merge (do not squash) so the tagged commits
0.0.15.3/0.0.15.4remain inmain's history and the tags stay valid.Follow-up
A separate PR for
errorMessageImprovement(thegenerateErrorReportfeature, bumped to0.0.16) is stacked on top of this and will be opened once this merges.🤖 Generated with Claude Code