#27230: Inconsistency in AppConfig.path depending on sys.path
--------------------------------+--------------------------------------
Reporter: vinayinvicible | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: 1.10
Severity: Normal | Resolution:
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 aaugustin):
Well, given that the issue doesn't exist in Python 3, is fixed in Django
2.7.12+, and that we're dropping support for Python 2 in six months:
https://www.djangoproject.com/weblog/2015/jun/25/roadmap/:
> Django 1.11 is likely to be the last version to support Python 2.7 as it
will be supported until the end of Python 2 upstream support in 2020.
absent other reasons, it doesn't seem reasonable to me to change the
return value of AppConfig.path from a relative to an absolute path, which
could cause issues with projects that use this value.
--
Ticket URL: <https://code.djangoproject.com/ticket/27230#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.9a1aa0921ecf382a1cf38b1ac73d79a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
