+1 on the idea for better inline docs, would be some relief for IDEs
figuring out a proper interface story boosting dev speed for rarely used
aspects, where currently one would have to search through the prosaic
online docs or end up browsing the django source.
On the other hand I am not sure, if that an easy task to accomplish
without bigger refactoring. Django uses a lot of bootstrap/runtime
patching under the hood, from custom metaclasses, explicit injection
pattern up to proxies at various ends. Currently IDEs often give up
here, idk if more inline docs alone can change much or if the level of
abstraction within django would have to change to get a significant
improvement.
Cheers,
Jörg
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/eea57151-576e-4b21-ae70-42a4e617565f%40netzkolchose.de.
