Due to the dynamic nature of Python, features aren’t obvious. Developers don’t know what features a class has unless they dig through the convoluted source code themselves or going online to check the documentation.
For example when implementing a `forms.ModelForm` hovering over it reveals absolutely nothing useful. [image: image] image1000×157 11.5 KB <https://global.discourse-cdn.com/business7/uploads/djangoproject/original/3X/d/f/df1eda85d38f5ff5978a7b966e2e4341bd45138a.png> What do the “Django Lords” have to say about inlining the documentation in the source code itself. I know the “Django Lords” have been weary of adding type stubs. However adding a docstring to this ``` class Model(models.Model): ... class Meta: <<<<< THIS ... ``` would require some stubs/.pyi files. I wouldn’t want to work on this just to find out that there are benefits of the current setup that they aren’t willing to make a tradeoff. What would be the best way of asking the Django Governing Board about their opinion on this? -- 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/d5ed6671-b8bb-4ce7-b3b8-15b2dd6796a9n%40googlegroups.com.
