I'd be against it. At work I deal with one codebase that's Django and one that's Flask/SQLAlchemy, so I've run into the issue of not being able to name a column 'metadata' in a SQLAlchemy ORM model (that name is reserved for SQLAlchemy's internal use, but not underscore-prefixed), and been frustrated by it. I don't know offhand if anyone would ever want to use 'meta' as a field name in a Django model, but making it impossible when Python provides a standard convention for indicating something is internal API seems like a bad idea.
-- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAL13Cg_tpzM%2BQogytXYzDBCpb6%3DZ2rFrPuJSUHUFcbgGZK9qBA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
