Question about provider/Python wheels: I'm using p...
# python
Question about provider/Python wheels: I'm using pipenv to install some dependencies... I noticed the slowest part when installing a venv is the grpcio wheel and other pulumi provider wheels... at least on my m1 mac.. I was wondering if anyone else noticed this, if this is normal, since there might be no published wheels for grpcio and the providers depend on it?
Anyway, this costs ~1-2 minutes of time on my machine, could be longer on less powerful ones. Not that significant, but in a CI set up this feels a little wasteful and wasn't sure what others' suggest for this?
I remember pip had an issue with the M1 architecture when it was released which didn't allow for the use of pre-compiled packages, not sure if it was ever addressed... I remember reading a couple of PEPs at the time, but didn't follow up later...
actually, never mind... I think I got it mixed up with the glibc/musl PEP around the same time M1 came out:
Do you have wheel installed in your global environment? It’s way quicker if you do
Not in the venv, it needs to be on your global python path
Are you saying to install the wheel globally (the package) so it gets pulled by pip for the venv, instead of rebuilding all the time?