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

Update dependency build123d to >=0.9,<0.10 #231

Merged
merged 4 commits into from
Feb 16, 2025
Merged

Update dependency build123d to >=0.9,<0.10 #231

merged 4 commits into from
Feb 16, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 15, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
build123d >=0.8,<0.9 -> >=0.9,<0.10 age adoption passing confidence

Release Notes

gumyr/build123d (build123d)

v0.9.1

Compare Source

Notable Changes

  • Enable citation of build123d in scholarly articles

Selected Other Changes

New Contributors

Full Changelog: gumyr/build123d@v0.9.0...v0.9.1

v0.9.0

Compare Source

Upgrade Steps
  • Due to some necessary changes to one of our key dependencies (cadquery-ocp), when upgrading build123d from approx. <=0.8.0 to 0.9.0, the VTK formerly provided by cadquery-ocp is not always cleanly removed. There are two known solutions to this (1) create a new clean environment, or (2) pip uninstall vtk then pip install vtk==9.3.1. See https://github.com/gumyr/build123d/issues/883 for any further updates.
Breaking Changes
  • Eliminate previously deprecated e.g. Shape.export_stl methods. Please use the appropriate function instead e.g. export_stl(Shape, "filename.stl")
  • While Part() + ... generates a Compound if needed as normal. Solid() + ... may return a ShapeList of Solids as Compound is not available for lower-order classes. Typically wrapping with Compound() is a usable workaround for these cases to approximate the old behavior. This change was necessary due to the refactor of topology.py.
  • surface.thicken(amount) → Solid.thicken(surface, amount). This aligns with the principle that lower-order classes cannot directly generate higher-order objects.
Major Notable Changes
  • Major refactor of approx 10k line topology.py primarily by @​gumyr and also others, split into multiple smaller files and eliminate circular references. Restructure topological shapes to depend only on lower dimensional shapes and clarify input and return types. (many commits)
  • Codebase now passes mypy static type checking primarily by @​gumyr and also others (many commits)
  • Dropped support for Python 3.9, and added support for Python 3.13
  • Added optional dependencies: ocp_vscode, development, docs, stubs, benchmark and all. You can install like pip install build123d[development]
  • shape.split(Keep.BOTH) now returns a tuple of Shape objects instead of a Compound.
  • Shape.extrude() has been replaced with topology-specific methods: e.g. Edge.extrude(vertex), Face.extrude(edge), ...
  • Shape.intersect() may now return None when no intersection is found.
  • Edge.intersect() has been enhanced to accept a Plane and return either Vertices or Edge (if fully contained within the plane).
  • Now depends on cadquery-ocp>=7.8,<7.9 which includes some internal changes to OCCT shape hashing
Selected Other Changes
New Contributors

Full Changelog: gumyr/build123d@v0.8.0...v0.9.0

Configuration

📅 Schedule: Branch creation - "before 3am on Saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate Renovate
Copy link
Contributor Author

renovate bot commented Feb 15, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock
Updating dependencies
Resolving dependencies...

Creating virtualenv yacv-server-WUdmF7De-py3.12 in /home/ubuntu/.cache/pypoetry/virtualenvs

The current project's supported Python range (>=3.9,<3.13) is not compatible with some of the required packages Python requirement:
  - build123d requires Python <3.14,>=3.10, so it will not be satisfied for Python >=3.9,<3.10
  - build123d requires Python <3.14,>=3.10, so it will not be satisfied for Python >=3.9,<3.10

Because no versions of build123d match >0.9,<0.9.1 || >0.9.1,<0.10
 and build123d (0.9.0) requires Python <3.14,>=3.10, build123d is forbidden.
So, because build123d (0.9.1) requires Python <3.14,>=3.10
 and yacv-server depends on build123d (>=0.9,<0.10), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For build123d, a possible solution would be to set the `python` property to ">=3.10,<3.13"
    For build123d, a possible solution would be to set the `python` property to ">=3.10,<3.13"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

@renovate renovate bot force-pushed the renovate/build123d-0.x branch 6 times, most recently from 9a98b08 to 83133a5 Compare February 16, 2025 02:40
@renovate renovate bot force-pushed the renovate/build123d-0.x branch from 83133a5 to 25628c9 Compare February 16, 2025 05:20
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Feb 16, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@Yeicor Yeicor merged commit 5f6b6d7 into master Feb 16, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Yeicor