#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
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
Hi Natalia, thanks for the response.
I shouldn't have used the word peformant (sorry!) as performance was not
the real motivation. The motivation was that it's simply less invasive to
avoid executing unnecessary modules. If you develop a project called
`presto` and decide to create a project `presto-helper` without the
knowledge that there's someone else's `presto-helper` already installed in
your environment, `presto-helper` will get executed, which could possibly
dump things to the terminal or execute queries (hopefully it wouldn't). It
just seems nicer to avoid that if there's a simple workaround.
I understand this is a judgment call since users are responsible for
what's installed in their environment, and if they install things that
have noisy import-time statements, that's not on Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/34778#comment:2>
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/01070189f944766b-1946ad32-c2a0-4c4b-97ef-6ad5f6bc228b-000000%40eu-central-1.amazonses.com.
