Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  (none)
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bcail):

 * cc: bcail (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018c59b36962-0fe216f3-934d-493e-87e6-315c4340a573-00%40eu-central-1.amazonses.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  Saeed
 |  Hasani Borzadaran
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Saeed Hasani Borzadaran):

 * owner:  (none) => Saeed Hasani Borzadaran
 * status:  new => assigned


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018292042d3e-a33c0d54-1d76-46b5-a91b-269610245afd-00%40eu-central-1.amazonses.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Saeed Hasani Borzadaran):

 * owner:  Saeed Hasani Borzadaran => (none)
 * status:  assigned => new


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701825777beaa-8ace5b80-59e5-47ff-a5a3-c949663be1dc-00%40eu-central-1.amazonses.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  Saeed
 |  Hasani Borzadaran
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Saeed Hasani Borzadaran):

 Dear Mariusz
 This would be a very cool feature to add to Django.
 I have enough time to do this and I am very eager to do it.
 Can you give me more guidance to get a good result (about connecting
 custom attributes to the migration framework)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181fc564ebd-4a236430-93a7-4e90-a784-573604ccb076-00%40eu-central-1.amazonses.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  Saeed
 |  Hasani Borzadaran
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Saeed Hasani Borzadaran):

 * status:  assigned => closed
 * resolution:   => needsinfo


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181fc4dc144-ec0a74c3-8f40-4e77-a110-79cc5536fd0a-00%40eu-central-1.amazonses.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  Saeed
 |  Hasani Borzadaran
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Saeed Hasani Borzadaran):

 I have studied a lot about the {{{ Meta }}} class.
 I disabled the typo section and added my new attribute, but unfortunately,
 I didn't get any results.

 About {{{ AppConfig.__init__() }}} , I honestly didn't understand and I
 need your guidance.
 Do you have enough time to explain more? Can you give me an example to
 implement it?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181f15eccf5-e8babb6f-9be3-4855-8a2c-d8656ad72ecc-00%40eu-central-1.amazonses.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  Saeed
 |  Hasani Borzadaran
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Loic Bistuer):

 Dear Saeed, typically that would be intended for reusable 3rd party apps
 to pick up rather than ordinary apps, but yes the idea is not to be
 limited to the built-in attributes.

 The main challenge is to find an elegant way to register new attributes
 (so the system that reports typos still works) and that kicks in at the
 right time to be useful, I mentioned above that I suspect
 `AppConfig.__init__()` will work but that would have to be checked.

 As Dylan mentioned, we also need to see how this interacts with the
 migration framework, especially the ORM inside RunPython.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181cfc586e6-c3fb040e-fe25-491f-a2cf-d9fb61b37554-00%40eu-central-1.amazonses.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  Saeed
 |  Hasani Borzadaran
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Saeed, I removed your comment because you remove the ticket description.
 Please don't do this.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181cfc2896f-87397949-d993-486e-87a8-58804708c12f-00%40eu-central-1.amazonses.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  Saeed
 |  Hasani Borzadaran
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Old description:

> In some cass it is useful to be able to store meta information on models
> inside the model class. In Django the Meta subclass is used to achieve
> this. Trying to add a custom attribute to a model's Meta inner class
> results in an exception though, thrown from django.db.models.options,
> which does indeed check any valid attribute names and raises an exception
> when unknown names are found.
> Is there any reason for this somewhat strange behaviour, not to allow a
> developer to add non-standard meta information to a model class (which
> can later on be used in eg view code)?
>
> Thanks!

New description:



--

Comment (by Saeed Hasani Borzadaran):

 Did I get it right?
 The Meta class now receives a series of fixed attributes. We want to make
 these features dynamic. Does it mean that the developer can add attributes
 to the class?

 If yes, can I contribute to this feature in Django 4 or not?

 Thanks

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181cfaf2219-93cf5a25-4e0c-4ada-97ca-b06093d13c9d-00%40eu-central-1.amazonses.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  Saeed
 |  Hasani Borzadaran
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Saeed Hasani Borzadaran):

 * owner:  nobody => Saeed Hasani Borzadaran
 * status:  new => assigned


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181cf614d8c-2642a2ef-a394-402d-95f5-3be6ade08075-00%40eu-central-1.amazonses.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by omelched):

 * cc: omelched (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.d8d2df67a1adaaf22a049d7185275a2a%40djangoproject.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Gordon Wrigley):

 * cc: Gordon Wrigley (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.c94a5c668c174b17544fadb1a742f7da%40djangoproject.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sardorbek Imomaliev):

 * cc: Sardorbek Imomaliev (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.f626786f7d7e87a303e263e612a49108%40djangoproject.com.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlos Palol):

 * cc: Carlos Palol (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.19107bc2da2ce2e2fb6873dc90d4b0be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Rich Rauenzahn):

 * cc: Rich Rauenzahn (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.993a24b09cf3ff9874cd67fb59014103%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ryan Hiebert):

 * cc: Ryan Hiebert (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.1fc8c85036568849275e991b2913938e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Dylan Young):

 This would actually enable users to develop on Django much more easily; I
 imagine you would get a slew of new ORM developments coming in quite
 quickly.

 Some thoughts:

 1) How to hook into the migration system for database changes?  i.e. If I
 wanted to add partial indices and have the migrations autogenerate from my
 custom Meta option for this. The 'register_option' idea is probably good
 for this.

 2) How to play nice with migrations for state changes?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.f91ffdc123b12a830371f31c9fab0e48%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Maxime Vdb):

 It would be indeed very useful: I have a custom database backend (for
 Redshift) and I would like to support advanced options for this backend
 (these options would modify the SQL for table creation for instance).
 There is apparently no other way than defining that on the Meta dict (due
 to the migration system) but it is not possible to define custom options.

 Did you guys agree on the design yet?

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.aa85c9b9c250ef8014e9d6a0225e7892%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Adam Chainz):

 James I think this ticket is about Model.Meta but whatever the API it ends
 up with could be copied over to ModelForm.Meta, so idk if it makes sense
 to create a second ticket for that yet

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.63523fc8fee87afe86b360b37180f00a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by James Pic):

 Question: is this ticket just about Model.Meta or also for ModelForm.Meta
 ? /me wondering if another, similar ticket could be opened about
 ModelForm.Meta

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.b6fb8b338fd85c0469694abe884dbdca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by James Pic):

 * cc: jamespic@… (added)


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.f80dbfca1cda0f14edf1b5b1d5f99b67%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by loic):

 * cc: loic (added)


Comment:

 How about an API to register new model options (e.g.
 `models.Options.register_option('mptt_manager_name')`).

 The `AppConfig.ready()` comes in too late to register this, but
 `AppConfig.__init__()` should work.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.289928a87645785d6c9b8de64273f753%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+-
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * component:  Metasystem => Database layer (models, ORM)
 * easy:  1 => 0


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.3fb469430c38d5975e7bf7d77ead4f6b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Metasystem   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by litchfield):

 * cc: litchfield (removed)
 * easy:  0 => 1


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.18996ea78b179353e0a941d87f74f22d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Metasystem   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by litchfield):

 * cc: litchfield (added)


Comment:

 +1 - it's kinda daft to encourage the ORM to be extendable, while at the
 same time restricting what Meta options we're allowed

 Why not just move DEFAULT_NAMES into the Model class? problem solved, zero
 breakage.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.5fb33f89d8f6af1d15bd1ca4356082b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Metasystem   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by bronger):

 Forget comment:9, I was wrong.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.5fb64fa6be68ac03f9c35321b3c76251%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Metasystem   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by bronger):

 The non-nested `MyApp` doesn't seem to be inherited.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.e85decc867fc0b79b637abaddc06cb19%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Metasystem   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by shai):

 Replying to [comment:7 shai]:
 > The point about extending the ORM stands, but this does not seem to be
 the use-case that motivates the current requests.

 I have to take that back -- it is true as far as the requests on the
 mailing list postings are concerned, but #21081 actually is about
 extending the ORM.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.0ac4322701b64b9c51052722a2291c34%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Metasystem   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by shai):

 On the list, Tim Chase gave this example:
 {{{
 class MyModel(Model):
   class Meta:
 ...
 class MyApp:
   secure_fields = ["cc_num", "ssn"]
 }}}
 The idea was that app-specific properties should be namespaced to avoid
 clashes. I think the approach is fine, I just don't see why these classes
 need to be in Meta; I see nothing wrong with

 {{{
 class MyModel(Model):
   class Meta:
 ...
   class MyApp:
 secure_fields = ["cc_num", "ssn"]
 }}}

 This leaves the app-specific metadata separate from fields and methods, so
 the "API" is clean enough; it avoids clashes reasonably well; and it
 requires no changes in Django.

 Note that this was the approach taken by Admin at first -- and my
 impression (though I wasn't "there" at the time) is that it changed
 because Admin classes became too large for comfort as nested classes, not
 because the first idea was considered so bad.

 I think for most use-cases -- in particular, including the two noted on
 the list, marking fields as "to be published" or "to be censored", this
 can work well.

 The point about extending the ORM stands, but this does not seem to be the
 use-case that motivates the current requests.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.7849da7a446f0c20680509a1da5d0ed0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
-+
 Reporter:  eikke@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Metasystem   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by russellm):

 * status:  closed => new
 * severity:   => Normal
 * resolution:  wontfix =>
 * easy:   => 0
 * ui_ux:   => 0
 * type:   => New feature
 * stage:  Unreviewed => Accepted


Comment:

 This ticket was raised on Django-developers in response to a duplicated
 report (#21081). The devil is in the details, but I can at least see that
 there is a use case here. I share @ubernostrum's concern about Meta
 becoming a dumping ground for flags that shouldn't be kept on Meta, but it
 doesn't follow that there is no reason why an end-user would want to
 define an extension to the built-in set.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.a83fb869794cc6567d74a9c573e3c61a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
--+-
  Reporter:  ei...@eikke.com  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Metasystem   |   Version:  SVN   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by robmadole):

 Inspired by the django-easytree code, I've created django-immutablefield
 for anyone interested.

 http://pypi.python.org/pypi/django-immutablefield

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
--+-
  Reporter:  ei...@eikke.com  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Metasystem   |   Version:  SVN   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by miracle2k):

 For those Googling, it turns out there is a way to work around this using
 a custom model metaclass:

 http://bitbucket.org/fivethreeo/django-
 easytree/src/7ab11cd55b09/easytree/models.py

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
--+-
  Reporter:  ei...@eikke.com  | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Metasystem   |   Version:  SVN   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * status:  reopened => closed
  * resolution:  => wontfix

Comment:

 If you disagree with a wontfix designation, the correct place to bring it
 up is on the django-developers list.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5793: Allow custom attributes in Meta classes

[Django]

#5793: Allow custom attributes in Meta classes
--+-
  Reporter:  ei...@eikke.com  | Owner:  nobody
Status:  reopened | Milestone:
 Component:  Metasystem   |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by miracle2k):

  * status:  closed => reopened
  * resolution:  wontfix =>

Comment:

 I'd like to ask this be given another thought.

 I'm not really convinced by the validation argument; first, this seems a
 more basic problem at it's core, particular in scripting languages. There
 are lots of places where a typo could lead to an API silently not being
 activated (think certain kwargs-scenarios, or a typo in the name of
 subclass methods etc). At some point you just need to actually check
 whether the code you've written actually does what its supposed to.

 Secondly, if one really wants meta-validation, there is a middle ground:
 Require custom meta attributes to be pre-registered.

 I just think this would be really nice for libraries that provide model
 base classes to accept configuration. Say for example django-treebeard and
 it's node_order_by (which is currently simply added to the class itself,
 which works, yes, but there's a reason why we have Meta in the first
 place).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.