Re: [Sqlalchemy-tickets] [sqlalchemy] #1631: pg8000 not working with enums.

[sqlalchemy <mi...@zz...>]

#1631: pg8000 not working with enums.
-----------------------------------+------------------------------------
      Reporter:  guest             |      Owner:  zzzeek
          Type:  defect            |     Status:  closed
      Priority:  medium            |  Milestone:  0.6.xx
     Component:  postgres          |   Severity:  no triage selected yet
    Resolution:  worksforme        |   Keywords:
Progress State:  completed/closed  |
-----------------------------------+------------------------------------

Comment (by zzzeek):

 Hm I guess he merged it after I had done the extra work?  I might have
 still been getting used to pull requests at that point.

 for Py2/3, the only rational choice is an in-place codebase.   all of my
 major libs/tools are now py2k/3k in place, no 2to3 needed - alembic,
 dogpile, mako, sqlalchemy as of 0.9.  mako in fact supports from py2.4 all
 the way to py3.4, and is very heavy on unicode as well as python
 interpreter internals even.   It's not very hard to make a pure-python
 codebase support between 2 and 3.

 the two paramstyles I think are important, and the ones we've decided on
 the DB-SIG list would be the standard in a DBAPI 3, are qmark and named.
 These two formats are commonplace outside of the Python world.

 my next choice would be format and pyformat.   I'm not too keen on
 numbered since it is just another named style, just more awkward.

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1631#comment:10>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python