-
Notifications
You must be signed in to change notification settings - Fork 973
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
Issue with pyproj as dependency #8177
Comments
Can you share the |
|
And what platform are you are? Like OS and architecture? Can you share |
I'm on a mac with Apple M1 Pro. Here are those logs: DEBUG uv 0.4.20 (Homebrew 2024-10-08) [stderr] |
I think it's because they only publish ARM Wheels for macOS 14 and later, but I assume if you're on an M1 you're on some version earlier than macOS 14? In which case, you have to build from source, and that source build is failing for reasons that are specific to the package. It looks like they provide some instructions in https://pyproj4.github.io/pyproj/stable/installation.html. |
yes, I think you've pinpointed it, if I could ask a final question then to check my understanding, I'm looking into migrating from a workflow based on declaring a new conda environment and pip installing into it to one built around uv and virtual environments. Expanding a little the example above (assuming things are a little more filled out but imagine essentially a similar
So here I was thinking |
What does |
Want to start with a big thank you for responding to my questions! To test this I made a small new folder for test_repo, with the files .python-version:
(Side note is hit a similar version with pyarrow, but going back from python 3.12 to 3.10 resolved this one) pyproject.toml:
And setup.py:
Running
Running with conda and pip:
yields: (see later comments) |
From those logs, it looks like pip is actually installing this project, rather than your own local project! https://pypi.org/project/test-repo/ |
I think you need |
yes sorry, just caught that, fixing now |
(not relavent) |
Hard to say how from these logs alone but it looks like
|
I will start fresh, sorry, one second, |
Okay so from those logs, it looks like the difference is that Conda was installed as x86 (notice that it selected https://files.pythonhosted.org/packages/e4/fa/8a769da6bb8e26b1028c19d048b88373a40bd8e17a893e07b9889d1aed03/pyproj-3.7.0-cp310-cp310-macosx_12_0_x86_64.whl.metadata) whereas |
Ok, yes, that makes a lot of sense. Appreciate very much your time and help! Will spend some more time now thinking about best way for us on this but much clearer now the difference. Thank you! |
No problem, thanks for being so responsive with my own questions. |
I'm going to close this as I think things are working as expected from our end, but you're welcome to ask more questions if they come up. |
That's perfect, thank you |
I have a small uv project that includes a pyproject.toml:
If I run on the command line:
uv sync
I have the output:
Following through the provided link, the variable mentioned is required when building from source, but is that what I'm doing in the above example? Thank you for any help!
The text was updated successfully, but these errors were encountered: