Re: making it feasible to rely on loaders for reading intra-package data files

Nick Coghlan <[email protected]> Mon, 3 Feb 2014 18:47:29 +1000
Newsgroups gmane.comp.python.import
Message-ID <CADiSq7fho2Z_783A-qJ_ZFmwXTnioFxcdrHENKe44F+4dO-jjQ@mail.gmail.com>
On 3 Feb 2014 00:05, "Paul Moore" <[email protected]> wrote:
>
> BTW, I keep geting moderated on this list. I just checked and I seem
> to be subscribed. Is there a problem somewhere? Or have I been blocked
> for some reason?

Maybe someone tried to make you a moderator and set your moderation flag
instead?

We accidentally did that to Victor on the core mentorship list :P

Cheers,
Nick.

>
> On 2 February 2014 13:50, Paul Moore <[email protected]> wrote:
> > On 1 February 2014 18:44, Brett Cannon <[email protected]> wrote:
> >> Over on distutils-sig it came up that getting people to not simply
assume
> >> that __file__ points to an actual file and thus avoid using open()
directly
> >> to read intra-package files is an issue. In order to make using a
loader's
> >> get_data reasonable (let alone set_data), there needs to be a clear
> >> specification of how things are expected to work and make sure that
> >> everything that people need is available.
> >
> > An alternative suggestion - now that Python 3.4 has pathlib, how
> > practical would it be to create a ZipFilePath subclass that acted as a
> > concrete path for files in a zipfile? Getting people to use pathlib
> > for dealing with __file__ rather than the old os.path functions might
> > be an easier sell, and if pathlib handled zipfiles "behind the scenes"
> > we could avoid the whole issue.
> >
> > Paul.
> _______________________________________________
> Import-SIG mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/import-sig

_______________________________________________
Import-SIG mailing list
[email protected]
https://mail.python.org/mailman/listinfo/import-sig