publish a wheel

[dimbleby]

I notice that this package publishes only a source distribution, so that every user has to build the wheel themselves. Better for package owners to build and publish wheels once and for all.

upload.sh looks as though it should do the right thing, so perhaps something went wrong?

[alashchev17]

During CI/CD workflow, got this error with py-vapid 1.9.3:

#21 7.375 Collecting py-vapid>=1.7.0 (from pywebpush->***************==0.1.0)
#21 7.380   Downloading py_vapid-1.9.3.tar.gz (10.4 MB)
#21 7.446      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 10.4/10.4 MB 167.4 MB/s  0:00:00
#21 7.672 ERROR: Invalid member in the tar file /tmp/pip-unpack-6gi_9f93/py_vapid-1.9.3.tar.gz: 'venv/bin/python' is a link to an absolute path
#21 ERROR: process "/bin/sh -c pip install -v -e '.[services]'" did not complete successfully: exit code: 1

Workaround: Pin to py-vapid<1.9.3 temporary.

[jrconlin]

Sigh, looks like the publish process changed as well.

I've pushed 1.9.4 which trims things down and (hopefully) includes the wheels.

Thanks!

[dimbleby]

Looks like you've published a wheel but not a source distribution. That's probably the less bad way round, but I guess not what you intended?

[jrconlin]

heavy, heavy sigh
This is what happens when you focus on a different programming language for a year or so while the other one goes through some radical changes.

Let me see what else changed since the last time I did any packaging in python.