Closed gordthompson closed 4 years ago
I would definitely appreciate your help in publishing this project on PyPi. Give me a a week or so.
I'll ping you when I'm ready to go. Thanks.
As a side note: I'm ready to drop the firebird2:// URI myself - it wouldn't cause any headaches.
I would definitely appreciate your help in publishing this project on PyPi. Give me a a week or so.
I'll ping you when I'm ready to go. Thanks.
Okay, great. The process should be almost identical to what I needed to do for sqlalchemy-access, and it was surprisingly easy.
I just did a test deployment to test.pypi.org and it seems to be working okay.
pip install -i https://test.pypi.org/simple/ sqlalchemy-firebird==0.0.1a1
gave me sqlalchemy-firebird, but I had to install the prerequisites (SQLAlchemy and fdb) first because they aren't available from test.pypi.org.
Hi Paul. If you've been working with this dialect for a while and are fairly confident that it is stable enough for public release then it would be a good idea to get this up on PyPI. In the reasonably near future SQLAlchemy will start warning users of the old internal Firebird dialect that it is deprecated and it would be nice to be able to let them know that they can
pip install sqlalchemy-firebird
.In a related note, I've been working with @zzzeek and the rest of the SQLAlchemy team on this issue that should help ease the transition. If the change is accepted then we should enable the
firebird://
URI prefix for this dialect before public release. (We can continue to supportfirebird2://
to avoid unnecessary headaches for you or anybody else who's been working with this.)I'd be happy to help out if you would like to proceed. Just let me know.