-
Notifications
You must be signed in to change notification settings - Fork 51
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
DEPRECATION: pyobjc-core is being installed using the legacy 'setup.py install' method #550
Comments
Thanks for the report, that's one I wouldn't have noticed until the deprecation turns into an error because my development environment always has wheel installed. BTW. Did you install from source by choice? In general the installation should use wheels from PyPI. |
To reproduce the issue: make sure a pip version before 23.1 is installed, with 23.1.1 installed the deprecation message goes away and pip uses the pyproject.toml build method (even with no such file in the archive). The installation appears to be successful. If I read the linked pip issue correct that's expected: as of 23.1 pip will assume the use of |
b37f380 adds a trivial pyproject.toml to all subproject to avoid the warning. This is fairly annoying busy work, but I guess that's the price of progress. |
That is mean for installation pyobjc 9.1.1, and pip version 23.1? |
1 similar comment
That is mean for installation pyobjc 9.1.1, and pip version 23.1? |
With recentish versions of pip before 23.1 you'll get a deprecation warning as mentioned the initial message for this issue, you can work around this by ensuring that The changeset I pushed earlier tonight explicitly opts pyobjc into the new method for building wheels to avoid problems later if the pip maintainers ever decide to drop the legacy build method. |
I used command |
Reopening because the minimal pyproject.toml somehow doesn't work for the framework bindings. The error says the 'pyobjc_setup' cannot be found, even though it is present in the checkout and sdist archives. |
Describe the bug
A clear and concise description of what the bug is.
pip install pyobjc
out of the box results in this error:Platform information
To Reproduce
pip install
will do it in a fresh environment, although you may needExpected behavior
To install using pyproject.toml I guess?
Additional context
I think installing the
wheel
package might also work around this issue, but it seems clear thatpip
is steering folks towardsThe text was updated successfully, but these errors were encountered: