[Python-Dev] Direction of PyChecker (original) (raw)
Guido van Rossum guido@python.org
Sat, 11 Aug 2001 08:52:16 -0400
- Previous message: [Python-Dev] Direction of PyChecker
- Next message: [Python-Dev] optimizing non-local object access
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Off topic] The same seems to be true for pydoc in http-serving mode. It just imports any .py on sys.path, when doco is requested for it. Although pydoc is really cool, this aspect scares me a bit... (I guess if the port pydoc is listening to is visible from the outside world, it better run as a user with very limited permissions, right?)
Yes, this bothers me greatly. I hope that someone will fix this.
(Hm, that makes me think that it may be a good practice to name scripts that are not supposed to be imported so that they can't be imported?)
Indeedy! (Or make sure they're noy on sys.path. :-)
--Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] Direction of PyChecker
- Next message: [Python-Dev] optimizing non-local object access
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]