Message213306
| Author |
ncoghlan |
| Recipients |
Jurko.Gospodnetić, barry, brett.cannon, eric.snow, ncoghlan, ned.deily, r.david.murray, takluyver |
| Date |
2014年03月12日.22:03:59 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CADiSq7coifJMwUxmwiC3Ga58ryW=sZpDqCkqh_cvitWGqQOnPw@mail.gmail.com> |
| In-reply-to |
<1394660461.82.0.193425093434.issue20884@psf.upfronthosting.co.za> |
| Content |
I'm not sure Brett's plan is such a great idea. If you look at the file
attributes in my demo above, they include a leading path element (based on
the executable location), so it *is* possible to use the pkgutil data
access APIs sensibly from a frozen module (and even when there's no path
component, I believe the recommended way of invoking pkgutil would fall
back to the current directory).
So I don't think we should decide what to do without first comparing the
behaviour of frozen pkgutil.get_data dependent code between 3.3 and 3.4. |
|