Yes, I know but it creates confusion for users and has resulted in at least two bug reports like https://code.djangoproject.com/ticket/25584. I suspect we'll see more reports and queries about it once 1.9 goes final so I'd like to avoid that as long as there isn't any downside to the proposed change.
On Saturday, November 28, 2015 at 11:05:59 AM UTC-5, Donald Stufft wrote: > > > On Nov 28, 2015, at 11:03 AM, Tim Graham <timog...@gmail.com <javascript:>> > wrote: > > Claude said, "I also encountered this error when using pip 1.5.6 (default > version in Debian stable)." I guess at least some people might not want to > upgrade system packages. > > Is your main opposition to the change a "purity" one? Sure, we could add a > pip version check, but I don't see any downside to the proposed change. > > > pip 1.5.6 will print the warning but it’s just a warning. Newer pips will > silence it. A failure to compile to .pyc never fails the install for pip. > > ----------------- > Donald Stufft > PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 > DCFA > > -- 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 post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/443288e6-5105-41f0-8496-ee955babafee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
