--
Ticket URL: <https://code.djangoproject.com/ticket/21845>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/21845#comment:1>
Comment (by carljm):
Is there some missing context to this ticket? Is it just the .py suffix
we're deprecating, or the script itself? If the latter, how are we
expecting people to run startproject?
--
Ticket URL: <https://code.djangoproject.com/ticket/21845#comment:2>
Comment (by mjtamlyn):
I believe it's the `.py` suffix. In order to make the script executable on
windows, we're now using a setuptools entry point. This is however
impossible with a `.py` suffix. (I think)
--
Ticket URL: <https://code.djangoproject.com/ticket/21845#comment:3>
--
Ticket URL: <https://code.djangoproject.com/ticket/21845#comment:4>
Comment (by apollo13):
Fwiw, we don't have to deprecate it and can just install both variants, if
we think the deprecation isn't worth it -- eg to many programs relying on
it.
--
Ticket URL: <https://code.djangoproject.com/ticket/21845#comment:5>
* cc: berker.peksag@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/21845#comment:6>
* severity: Release blocker => Normal
Comment:
Both variants are installed as of #21827. I tend to think deprecation may
not be worth it as it doesn't seem like we gain very much besides perhaps
reduced confusion from not having two ways to do the same thing). I'll
leave the ticket open, but I'm unmarking it as a release blocker.
--
Ticket URL: <https://code.djangoproject.com/ticket/21845#comment:7>
* status: new => closed
* resolution: => wontfix
Comment:
Doc updates were made in #23067. I'll close this for now until someone
comes up with a good reason why we need to deprecate the `.py` variant.
--
Ticket URL: <https://code.djangoproject.com/ticket/21845#comment:8>