Upload wheel

[sqlalchemy-bot]

Migrated issue, originally created by Jeroen Ruigrok van der Werven (@asmodai)

Hi Mike,

saw that you had already added wheel to your setup.cfg, but could you also upload the wheels to PyPi?

Simple matter of running: python setup.py bdist_wheel upload

Thanks!

[sqlalchemy-bot]

Michael Bayer (@zzzeek) wrote:

currently we cant do wheels for either SQLAlchemy or Mako, Alembic's two dependencies.

What is it that you can't accomplish right now with a regular source distro? alembic has no C code to build.

[sqlalchemy-bot]

Jeroen Ruigrok van der Werven (@asmodai) wrote:

Ah, that makes sense.

No, I can use it just fine, merely thought it was an oversight. Mea culpa. :)

Let me close this issue since it doesn't make sense to keep it open.

[sqlalchemy-bot]

Jeroen Ruigrok van der Werven (@asmodai) wrote:

Mistakenly thought the wheel was not uploaded due to omission. That is not the case.

[sqlalchemy-bot]

peterbe (@peterbe) wrote:

I see no wheel uploaded on pypi.

Also, what difference does it make that SQLAlchemy and Mako can't do wheels? Can't alembic be wheel and it's dependencies continue to be tarballs?

[sqlalchemy-bot]

Michael Bayer (@zzzeek) wrote:

I have a consistent release process for all my packages and adding wheels to pypi is extra things for me to worry about, if some incompatibility or whatnot arises. pip already creates and caches wheels now, wheels are terrific for local package caching, for delivery via pip im not seeing the big win other than publishing pre-built C libs for platforms like Win32 etc.

[sqlalchemy-bot]

Changes by Jeroen Ruigrok van der Werven (@asmodai):

• edited description

[sqlalchemy-bot]

Changes by Jeroen Ruigrok van der Werven (@asmodai):

• changed status to closed

[youtux]

Hello, I see that both sqlalchemy and mako provide wheels now, would it be possible to upload the wheels also for alembic? It cuts down some build time when installing it on environments that don't use a shared system cache (e.g. docker containers).

[zzzeek]

if Mako has a wheel it's because someone had me run "bdist wheel" manually. I would have to update my release scripts for wheels to be consistent or perhaps @CaselIT can add a github action to this repo to do such (that's how SQLAlchemy wheels work).

[CaselIT]

Since alembic and mako are universal wheels (I think) it should be very easy to setup :)

[layday]

The last version to have had a wheel published on PyPI was 1.5.2 on 20 Jan - was re-dropping wheels intentional?

The latest version of Mako (1.1.4) doesn't have a wheel either although 1.1.3 does.

[zzzeek]

I've just not integrated it into my build process as of yet, so I have to remember to do it.

SQLAlchemy has wheels integrated via github actions and alembic and mako could use this as well.

[zzzeek]

well at least there is "pip wheel" and "twine upload" now so I can do the whole bunch of them at once without unpacking anything.

[CaselIT]

I can add a workflow to create it on release. it would be more or less the same as this proposal for the sphinx extension https://github.com/sqlalchemyorg/zzzeeksphinx/pull/2

[layday]

Do you sign the sdists, or why do you prefer to build and upload the sdists locally and the wheels on GHA, if you don't mind me asking?

[zzzeek]

the wheels are on GHA because github supplies a whole swarm of OSes including windows and OSX to build C code on every possible platform for SQLAlchemy. for pure Python wheels I would basically have to add a few lines to my local "create_release.sh" script, have not gotten around to it.

[CaselIT]

we seem to have added it at some point, since recent releases have them https://pypi.org/project/alembic/#files