[Python-ideas] Fixing __file__ to be absolute

[Brett Cannon]

On Thu, Jan 2, 2014 at 7:37 AM, Tal Einat <taleinat at gmail.com> wrote:

> On Wed, Jan 1, 2014 at 9:01 PM, anatoly techtonik <techtonik at gmail.com>
> wrote:
> > Fixing this thing will make my happy (or very sad if you'd like this).
> >
> > Problem is described here:
> > http://stackoverflow.com/a/6416333/239247
> > Summary:
> > 1.  chdir()
> > 2.  dirname(__file__)
> > 3.  FAIL
> >
> > Proposal:
> > from __future__ import abs__file__
>
> Anatoly, this subject was already discussed on this list, just three
> months ago, in a thread you started! [1]_
>
> To quote one of Nick Coglahan's replies [2]_:
>
> > Note that any remaining occurrences of non-absolute values in __file__
> are
> > generally considered bugs in the import system. However, we tend not to
> fix
> > them in maintenance releases, since converting relative paths to absolute
> > paths runs a risk of breaking user code.
>
> > We're definitely *not* going to further pollute the module namespace with
> > values that can be trivially and reliably derived from existing values.
>

This was also changed in Python 3.4 back in October:
http://hg.python.org/cpython/rev/76184b5339f2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20140102/fc74088f/attachment.html>