Rob Bairos rbai...@gmail.com added the comment:
Yah, thinking about this further, the real error is that sys.meta_path allows
processing of names with #,?* etc.
I can see why this would cause problems, as python names must only be _ and
alphanumeric characters.
I'll re-implement this.
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13314
___
___
Python-bugs-list
Brett Cannon br...@python.org added the comment:
This is working as intended. Importers on sys.meta_path should be able to rely
on the assumption that the names they are given are syntactically proper module
names and not just any random string. You could perform a transform from module
name
Rob Bairos rbai...@gmail.com added the comment:
Why is a module name syntactically improper simply because it contains a slash?
That seems an arbitrary definition, that serves no purpose, except to
discourage accidentally specifying a filename.
Module with unusual characters all reach the
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +brett.cannon, ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13314
___
___
New submission from Rob Bairos rbai...@gmail.com:
When adding hooks to sys.meta_path, to correctly deal with arbitrarily named
non-disk module definitions, module names with slashes should still be
processed.
As it stands when executing statements such as:
import my_module_123#/123
or
even
Changes by Rob Bairos rbai...@gmail.com:
--
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13314
___
___
Python-bugs-list mailing
Changes by Eric V. Smith e...@trueblade.com:
--
nosy: +eric.smith
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13314
___
___
Python-bugs-list
