Closed manuel-koch closed 9 months ago
I noticed that master branch is a lot ahead of latest released version of distance3d
.
Maybe this is already fixed, but not available on PyPi ?
Open3D was a dependency for a long time already. But it is not required for all components. Mostly for loading meshes and visualization. If you like to open a pull request, you can make it optional by moving it to extra_requires
. Note to myself: I have to find out which parts actually require Open3D.
The problem is that Open3D is usually not compatible with the latest Python version. So switching to an earlier version is another solution.
A hotfix would be to use pip install --no-deps
(not sure if that is the correct syntax though).
In any case I have to make a new release soon. I just didn't do it because I am working with the master branch.
I'm not using latest python version in the example above ( example=3.10 vs latest=3.12 ).
Strange, Open3D 0.18 supports Python 3.8 - 3.11 according to the website.
I'm not using latest python version in the example above ( example=3.10 vs latest=3.12 ).
Are you sure?
requires-python = ">=3.10"
would also include 3.12.
Ah, I see, the line requires-python = ">=3.10"
from the project.toml
actually allows using Python 3.12 for the hatch environment.
I'll try to pin that to 3.10 and see if it works.
Thanks for the hint !
Tweaking the project.toml
with the following snippet fixed the issue for me:
[tool.hatch.envs.default]
python = "3.10"
Thank you for the quick response !
I'm trying to setup a new python environment and installing
distance3d
doesn't work for me anymore. I was usingdistance3d
earlier with the same version range (>=0.8,<1.0) on my computer successfully. Isopen3d
a new (mandatory) requirement ?Using the following simple project definition fails for me, running on macOS 14.3.1 (23D60), arm64:
project.toml
Trying to setup the environment fails:
My project wants to use Python 3.10. I don't see why it couldn't find a matching
open3d
version given the previous pip output. All of the following versions seem to be compatible with my Python interpreter ( as far as details in the pip output are stating ):