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.

Sign up for GitHub

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

Jump to bottom

fix: add explicit dependency on rigetti-pyo3's "time" feature #476

Merged
merged 2 commits into from
Jun 14, 2024
Merged

fix: add explicit dependency on rigetti-pyo3's "time" feature #476

merged 2 commits into from
Jun 14, 2024

Commits on Jun 14, 2024

  1. fix: add explicit dependency on rigetti-pyo3's "time" feature 

    In rigetti/rigetti-pyo3#45 (and rigetti/rigetti-pyo3#46), I moved all
references to the Python time types under the "time" feature.  This
was a bugfix, but I didn't realize it was also a breaking change – any
library that relied on the time types implicitly being available would
break, just as this one did!  This adds the missing feature
dependency, and I've also upgraded rigetti/rigetti-pyo3#46 to be a
breaking change.

This commit also updates Cargo.lock to force the update to
rigetti-pyo3, meaning that builds will fail without the substantive
change.
    @antalsz
    antalsz committed Jun 14, 2024
    Configuration menu
    Copy the full SHA
    08ec8a5 View commit details
    Browse the repository at this point in the history

  2. fix: only update Cargo.lock for rigetti-pyo3 

    Updating the other dependencies brings in new licenses (Unicode-3.0), which is
probably fine but not something we need to figure out right now.
    @antalsz
    antalsz committed Jun 14, 2024
    Configuration menu
    Copy the full SHA
    03490b9 View commit details
    Browse the repository at this point in the history