-
Notifications
You must be signed in to change notification settings - Fork 41
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
Scorched earth 2 #184
Scorched earth 2 #184
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we need to fix the conflict first.
@evshary I've updated the years because it has been rewritten from scratch, so I think it's pertinent. |
Roughly adapt the code to the new PyO3 API, with a few warning fixes.
* fix(examples): fix commented parts of z_put.py * fix: apply PR reviews * fix: apply PR reviews
* build: Get Read the Docs release number from Cargo manifest This avoids hardcoding the release number in the documentation build config, making it easier to bump the version by only modifying the manifest. * build: Require Python 3.11 in Read the Docs configuration Python 3.11 is needed to access tomllib; useful for parsing the Cargo manifest file. * feat: Create branch, bump version and tag in release workflow * feat: Add publish-github job * fix: Broken tag dependencies * chore: Remove enforce-linking-issues workflow * fix: Bump version in pyproject.toml * chore: Upgrade artifact actions from v3 to v4 * fix: Typo in git-commit command * fix: Support jq 1.6 ubuntu-22.04 runners use jq 1.6 which doesn't recognize a dot for `[]` value iterator. See: jqlang/jq#1168. * Revert "chore: Upgrade artifact actions from v3 to v4" This reverts commit a535971. * fix: Build wheels from release branch * fix: Switch to pypa/gh-action-pypi-publish@release/v1 The older actions doesn't recognize the pyproject.toml metadata fields.
Complete rewriting using only Rust code (and Python stub)
The doc rendition is not good, because it doesn't seem to take in account the change that I made in .readthedocs.yml. I've tested it on my side, and it works fine. |
Tests doesn't pass because it seems I've resolved a bug, which was taken in account in the tests. In fact, some tests was not able to be stopped with |
The tests doesn't pass yet because of the deadlock issue in the examples. It's caused by relying on pseudo-RAII while exiting tests with an exception, which causes finalizers to run while Python interpreter is shutting down. |
@wyfo Please change the base branch to dev/1.0.0 as protocol_changes is no longer the development branch. |
Complete rewriting using only Rust code (and Python stub)