Thanks Mike. This sounds great although I have to admit that I don't follow it completely as I have not used authored anything via setuptools. If this is trivial for you, could you sketch out what this would look like?
pjjH On Mar 10, 11:25 am, "Michael Bayer" <mike...@zzzcomputing.com> wrote: > you can install the dialect using a setuptools entry point. SQLAlchemy > looks for dialect modules using the "sqlalchemy.databases" entry point > name, so in this case you might name it "sqlalchemy.databases.sybase-ase". > > phrrn...@googlemail.com wrote: > > > Hi, > > I have done a fair bit on a Sybase ASE dialect for Alchemy and it is > > now in a primitive but usable condition for simple applications. My > > employers are fine with contributing the code back to the project and > > I intended to coordinate with Mike Bayer about this shortly. In the > > meantime, we would like to deploy the driver locally and work out some > > of the bugs. Ideally, we would like to do this separately from our > > centralized SQL Alchemy installation as the release cycles for > > production s/w are much longer than the anticipated cycles for the > > Sybase dialect.Is it possible to use a dialect located outside the > > main installation by something as simple as the connection URI? > > > Have any of you similar situations? Have you any suggestions on ways > > to address this issue? > > > pjjH --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
