#34778: startproject could use find_spec() rather than import_module() to check
for
conflicts
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Management | Version: dev
commands) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* status: new => closed
* resolution: => needsinfo
Comment:
Hello Jacob, thank you for your ticket.
As a general rule, in order to decide about changes that would impact
performance, the usual advice is to provide, next to the change, some
evidence that the change will actually improve the performance. To do so,
one option is to use https://github.com/django/djangobench.
For this specific suggestion, and considering that `startproject` is used
once per project setup, I find it hard to justify to change the code on a
script that a django user may run 10? 50? 100? times in their career (I
personally have run `startproject` less than 50 times since 2005). Do you
have a use case where the performance of `startproject` is causing issues?
Cheers, Natalia.
--
Ticket URL: <https://code.djangoproject.com/ticket/34778#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070189f8f8e838-a5b45871-a605-4475-b8ca-b4a2f7d00e6f-000000%40eu-central-1.amazonses.com.
