Error on pip install bpy 4.1 #120181
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#120181
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: OSX 14.4.1
Graphics card: M2 Max
Blender Version
Broken:
4.1
Worked:
4.0
Short description of error
When installing bpy 4.1, errors are shown and package is not installed.
I'm using pyenv and version 3.11.2 is active.
Exact steps for others to reproduce the error
pyenv install 3.11.2
pyenv global 3.11.2
(verified 3.11.2 is active)
pip install bpy
ERROR: Ignored the following versions that require a different python version: 2.82.1 Requires-Python >=3.7, <3.8
ERROR: Could not find a version that satisfies the requirement bpy (from versions: none)
ERROR: No matching distribution found for bpy
According to https://pypi.org/project/bpy/, it is expecting python v 3.11.* which is installed and active (to the best of my knowledge)
Related to #119237 , but looks like I'm using pyenv instead of pipenv.
I've seen pip get confused about the exact version of python before, give
python -m pip install bpy(could be python3 on linux/mac unsure) a whirl.I gave it a whirl, but have the same response.
According to this bpy 4.1 doesn't exist...
According to this, the version it's trying to download is 2.82.1... Shouldn't pip be looking for the latest?
is
python -m pip -v install bpy --log log.txtshedding any light on the package selection process?can you attach the resulting log.txt?
I'm getting the same error, M2 Max, MacOS Sonoma 14.4.1.
I create a python 3.11 environment with anaconda:
When I run any combination of:
I get the error:
verbose output
The verbose output mentions that you can run
pip debug --verboseto get a set of compatible tags that it will scan https://pypi.org/simple/bpy/ for. Can you upload the output of the command?Since Blender 4.1 uses Python 3.11, this output unfortunately does not help if you generated it in an Python 3.10 environment (afaik).
Yes. Sorry. I've updated the output above
the issue appear to be it only lists
cp311-cp311-macosx_11_0_arm64while the blender package is named asbpy-4.1.0-cp311-cp311-macosx_11_2_arm64.whli found a similar ticket on the pip tracker which appears to be blaming pip from homebrewI'm having the same problem.
Apple M2 Max
OSX 13.5
I also have this issue.
Apple M1 Pro
macOS 13.6.4 (22G513)
I use
pdmto manage my Python projects and this is what I get when I create a new Python 3.11.8 project using the latest version ofpdmand try to use it to addbpyto my project:Command Output
And this is what happens when I instead try using
pipwithin the venv to installbpy:Command Output
For
bpy==4.0.0this all worked fine.@LazyDodo Is it possible that the platform tag on the wheel is wrong somehow? From your comment, when I look at the output, I see that it finds this version:
But when I run
pdm run python -m pip debug --verbose | grep "11_2"I get no results. The closest tag that is supported appears to becp311-cp311-macosx_11_0_arm64.not a mac user, but what i got from the ticket i posted is that the problem is the tag being missing on the pip side, not the tag being incorrect on the package.
I was able to install the wheel directly by changing the name:
@LazyDodo Hmm, so you think that the issue is that
pipdoesn't support the tagcp311-cp311-macosx_11_2_arm64when it should? I am using the latest version ofpip, so it seems surprising that it would be missing that..Seems that maybe it has something to do with the way that Python was built (I use
mise(previously calledrtx) but for this example, I tried usingpdmto install its own version of Python).These two issues seem to give more context:
https://stackoverflow.com/questions/76918323/pip-cannot-install-some-python-packages-due-to-missing-platform-tag-in-m1-mac
https://github.com/microsoft/onnxruntime/issues/17166#issuecomment-1693938597
I will also try to install using the official Python build and
venvto see if that works.Edit: It also does not work when using a
venvcreated using the official Python version downloaded from python.org.Hi there!
Same problem here, I've tried
on a MacBook Air M3 and got
Thanks a lot to anyone investigating this issue! :)
@LazyDodo Further investigation:
I opened an issue on the
pdmgithub page and the author suggested that the issue is actually on the Blender/packaging side due to an incorrect tag: https://github.com/pdm-project/pdm/issues/2824They also linked to this issue on the
packaginglibrary, which also seems to support this: https://github.com/pypa/packaging/issues/435I'll go ahead and confirm this at least. However, I'm not sure what the correct outcome is because the requirement of 11.2+ was explicitly done [1] to mitigate some Metal GPU issues on older Intel Macs. So from that angle we are correct to set our minimum to 11.2 and the statement from the
packagingissue of a "...promise that all 11.x wheels will be compatible" is false in this particular case.We could either set the package minimum to 11.0 and hope that Intel Macs never hit the GPU issue we worried about when using
bpy. Or set the minimum to 11.3+ and hope that folks can just upgrade?CC @ideasman42 for PIP related packaging issues
[1] Commit
ac708cb33aThe issue here is that the wheels uploaded to PyPi have the wrong Python version requirement. To verify, download one of the wheels from here then run:
Then navigate to
bpy/bpy-4.1.0/bpy-4.1.0.dist-info/WHEELand see the tag:Somehow the wheen was built to require Python 3.9 even though it should be 3.11.
EDIT: I can also confirm that the version tag
11_2prevents the wheel from being installed bypip, even after updating the CPython version requirement.@olokobayusuf That's interesting, since I was able to install it into a Python 3.11 venv by just changing the name of the wheel file.