Re: PyCon 2013 -- tentative title/abstract/outline -- feedback plz - v.2
> >I could start with this one of cause ;) but I hope they all know about
> >it by now. On a related note though: __file__ -- are we all friends
> >again ? ;)
> Not sure what you mean about enmity with __file__, but note that as of the
> acceptance of PEP 420 (namespace packages), in Python 3.3, __file__ is
> completely optional as an attribute of module objects.
I just vaguely remember that there were problems in some projects relying on
__file__ (some times opportunistically with os.path.realpath) to deduce the
path to other components of the project, which might had been symlinked
elsewhere ;-) and that is what dh_python has addressed:
Date: Fri, 15 Jan 2010 11:58:56 +0100
From: Piotr Ożarowski <piotr@debian.org>
To: debian-python@lists.debian.org
Subject: Re: new dh_python proposal
...
* broken modules that use __file__ incorrectly will work without problems,
--
Yaroslav O. Halchenko
Postdoctoral Fellow, Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
Reply to: