<p dir="auto"><strong>Migrated issue, originally created by Michael Bayer (<a href="https://github.com/zzzeek">@zzzeek</a>)</strong></p>
<p dir="auto">that is, all the functions in <a href="http://www.postgresql.org/docs/9.4/static/functions-json.html" rel="nofollow">http://www.postgresql.org/docs/9.4/static/functions-json.html</a> need to be possible without building subclasses of functions.</p>
<p dir="auto"><strong>Migrated issue, originally created by Frazer McLean (<a href="https://github.com/RazerM">@RazerM</a>)</strong></p>
<p dir="auto">As mentioned in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="384636807" data-permission-text="Title is private" data-url="https://github.com/sqlalchemy/sqlalchemy/issues/3746" data-hovercard-type="issue" data-hovercard-url="/sqlalchemy/sqlalchemy/issues/3746/hovercard" href="https://github.com/sqlalchemy/sqlalchemy/issues/3746">#3746</a>, Windows wheels on PyPI would be useful.</p>
<p dir="auto">I quickly set up wheel building on AppVeyor as a proof of concept. It's using my GitHub repository but it supports Bitbucket too.</p>
<p dir="auto"><a href="https://ci.appveyor.com/project/RazerM/sqlalchemy/build/1.0.3" rel="nofollow">https://ci.appveyor.com/project/RazerM/sqlalchemy/build/1.0.3</a></p>
<p dir="auto">I'd be willing to put the wheels on PyPI for new releases, but it's worth discussing user expectations. Once wheels are available, users expect them to be available. As such, it's good to have wheels on PyPI as soon as a new release goes live, and we'd have a delay if someone else is uploading.</p>
<p dir="auto">AppVeyor has a REST API, so I could create a script that downloads the build artifacts (i.e. the wheels) so that whomever does the release can also upload the wheels at the same time.</p>