it seems these are just a better type of NamedTuple so I would say certainly not:
"There have been numerous attempts to define classes which exist primarily to store values which are accessible by attribute lookup. " These classes look a lot more like result rows that are updateable, rather than mapped objects. Looks like it would be good for a system like Records: https://github.com/kennethreitz/records On Wed, Feb 28, 2018 at 3:37 PM, Seth P <set...@outlook.com> wrote: > I don't have a well-formulated question, but reading PEP 557 > (https://www.python.org/dev/peps/pep-0557/) made me wonder if SQLAlchemy > declarative models would/should in some way be Python 3.7 data classes. > > -- > SQLAlchemy - > The Python SQL Toolkit and Object Relational Mapper > > http://www.sqlalchemy.org/ > > To post example code, please provide an MCVE: Minimal, Complete, and > Verifiable Example. See http://stackoverflow.com/help/mcve for a full > description. > --- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sqlalchemy+unsubscr...@googlegroups.com. > To post to this group, send email to sqlalchemy@googlegroups.com. > Visit this group at https://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/d/optout. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.