Comments (11)
if you want to use module wheel.pep425tags use this wheel version
pip3 install wheel==0.34.1
from buildout.wheel.
Curiously, the thing from pip
that buildout.wheel
needs is exactly the same pip.pep425tags.get_supported()
function that Matthew Brett is missing earlier in that thread:
https://mail.python.org/pipermail/distutils-sig/2018-April/032178.html
I expected this would happen when I first heard the announcement.
However, since setuptools learned how to install wheels
by itself not long after the last release of buildout.wheel
and, consequently, Buildout can work with wheels without buildout.wheel
, I think people affected by this issue are better off upgrading setuptools and Buildout, and removing buildout.wheel
from extensions
.
from buildout.wheel.
Buildout can work with wheels without buildout.wheel, I think people affected by this issue are better off upgrading setuptools and Buildout, and removing buildout.wheel from extensions.
Hi @leorochael. Can you point me the right way to do this? I must install only binary packages and I can't find how to do that w/o the wheel extension.
Thanks.
from buildout.wheel.
@papachoco, please try to get to a minimal buildout.cfg
that reproduces this issue.
Then try upgrading buildout and setuptools, and removing buildout.wheel
from the extensions
setting in your buildout.cfg
and see if the problem persists. If not, see if your installation was done with wheels.
Unlike buildout.wheel
, when Buildout uses setuptools
to install wheels natively, they are converted into eggs, so the only way to know that wheels were used in buildout is to run with -v
and pay attention to whether a source distribution is being downloaded and built or whether a wheel file was downloaded and unpacked.
We might have to officially deprecate buildout.wheel
on Buildout itself, like buildout-versions
and
buildout.dumppickedversions
.
from buildout.wheel.
pip 10 moved all of its internal APIs so that people would stop importing them. See this thread: https://mail.python.org/pipermail/distutils-sig/2018-April/032181.html
I think there are going to be at least two steps involved for most
projects affected by the API change:
- The quick fix to add pip 10 compatibility (which is likely a matter
of "copy the code you need into the project that needs it")- The technical debt reduction to reduce code duplication (which is
likely a matter of "add the required APIs to the 'packaging' project")Step 2 is the step that the pip internals refactoring is designed to
encourage, as we believe a lot of tool developers were just using
pip's internal APIs rather than filing RFEs and submitting PRs to help
guide the evolution of the stable APIs in packaging in a use-case
driven manner.
from buildout.wheel.
AFAIU it should be happening automatically, if you have sufficiently recent zc.buildout and setuptools versions.
from buildout.wheel.
Tested with latest setuptools and zc.buildout and installing from wheel seem to work - installing lxml is a snap instead of compiling like in old setuptools without buildout.wheel. This also seem to fix #17 and buildout/buildout#407.
from buildout.wheel.
Hi. Tested successfully w/o using the script bootstrap.py
($ pip install buildout
then $ buildout
in the directory). Why this script still uses ez_setup.py
? Do I need to remove definitively this way to launch buildout?
from buildout.wheel.
Please don't deprecate this project yet. setuptools is still buggy and fails to install some wheels (e.g. pypa/setuptools#1362 and pypa/setuptools#1350). buildout.wheel
works correctly. Please fix the problem with the newer pip
and keep this project alive.
from buildout.wheel.
@wiggin15, I can relate, but this can only be fixed in buildout.wheel
if we can import pep425tags.get_supported()
from somewhere canonical. I'd be -1 on any attempt to fish this information from internal pip APIs again.
The first time around, I used pip.pep425tags
because it was either that or copying that information somewhere else.
Back then I tried to do the right thing back then by moving pep425tags
to packaging
(See pypa/packaging#83), but it got bogged down in "trying to design the perfect API" or something.
If you want to see buildout.wheel
move forward, then please make sure we can import get_supported()
from somewhere... supported....
from buildout.wheel.
Well, it looks like setuptools
got tired of waiting and decided to fork pep425tags
.
We could provisionally import it from there.
I'd be ok with a PR doing that and removing the pip
dependency as, presumably, if pip gets around to moving pep425tags
into packaging
, then setuptools would just carry it vendored as well.
from buildout.wheel.
Related Issues (8)
- Error when installing a wheel on Windows HOT 5
- Cannot install wheel from local file system if name not all lowercase on Windows HOT 1
- Wheel blacklisting HOT 1
- Only fall back to wheel if no other dists HOT 2
- Installing from wheel failed after upgrading to setuptools v38.2.0 HOT 7
- Please rename repo to buildout.wheel HOT 4
- Add manylinux test
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from buildout.wheel.