Please try to make it easy to understand the issue without looking at tickets and pull requests. Even after I did that, I couldn't find why you believe it should be a warning and not a comment. Why is this situation different from all the other places Django uses comments to indicate where introspection may not be perfect?
Wouldn't a warning break the documented usage of inspectdb because there would be non-Python text in models.py from the warning output? $ python manage.py inspectdb > models.py On Tuesday, December 1, 2020 at 9:12:53 AM UTC-5 damio wrote: > Hi, > > I got some feedback on the ticket that I should use comments to display > the warning instead of stderr, since I don't really agree with that, I'm > requesting more feedback to know which way I should do it. > > Ticket: https://code.djangoproject.com/ticket/32234 > PR: https://github.com/django/django/pull/13736 > > Thanks, > Damien > -- 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/b455bb92-6b91-4f2f-bdaa-8932d3cb2893n%40googlegroups.com.
