Bugs item #693255, was opened at 2003-02-25 14:44 Message generated for change (Comment added) made by bcannon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=693255&group_id=5470

Category: None Group: None Status: Open Resolution: Fixed Priority: 5 Submitted By: James P Rutledge (jrut) Assigned to: Just van Rossum (jvr) Summary: 2.3a2 site.py non-existing dirs

Initial Comment: In Python 2.3a2 the site.py leaves non-existing directories in sys.path.

On my Debian Linux system, using Python 2.3a2, the sys.path, after site.py is executed during interpreter initialization, includes the entry

/usr/local/lib/python23.zip

although no such directory currently exists on my system.

The module documentation contained in site.py does state

"Non-existing directories (or non-directories) are never added to sys.path"

----------------------------------------------------------------------

Date: 2004-03-21 06:33

Message: Logged In: YES user_id=357491

OK, the change was backed out.

----------------------------------------------------------------------

Comment By: Just van Rossum (jvr) Date: 2004-03-20 23:49

Message: Logged In: YES user_id=92689

As I wrote before, the _docs_ are wrong, site.py should NOT remove non-existing elements, since they may be non-file system items to be handled by a custom importer.

----------------------------------------------------------------------

Comment By: Brett Cannon (bcannon) Date: 2004-03-20 13:42

Message: Logged In: YES user_id=357491

In Python 2.4, rev. 1.59 has site.py remove non-existing paths.

----------------------------------------------------------------------

Comment By: Brett Cannon (bcannon) Date: 2003-07-07 21:11

Message: Logged In: YES user_id=357491

Can someone with more experience with the "official" policy of of site.py say whether or not the docs should be changed or site.py itself?

----------------------------------------------------------------------

Comment By: James P Rutledge (jrut) Date: 2003-05-29 12:20

Message: Logged In: YES user_id=720847

I do not know what policy is desired for the condition of the path after executing site.py.

I found the problem when I switched to try 2.3 and used an application I wrote which searches the path to obtain information about installed modules. During troubleshooting, the change in site.py from 2.2 to 2.3, to stop removing non-existent directories in the path, became evident as the reason for the application finding a non-existent directory in the path.

The application was, of course, easily changed to skip non-existent directories. The question is whether removing of non-existent directories in the path _should_ be done by site.py

----------------------------------------------------------------------

Comment By: Brett Cannon (bcannon) Date: 2003-05-28 18:33

Message: Logged In: YES user_id=357491

I take it the docs are what needs to change and not site.py?

----------------------------------------------------------------------

Comment By: Just van Rossum (jvr) Date: 2003-02-26 00:43

Message: Logged In: YES user_id=92689

The docs are indeed wrong.

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz) Date: 2003-02-25 19:08

Message: Logged In: YES user_id=33168

Just, does the doc still need to be updated?

----------------------------------------------------------------------

Comment By: James P Rutledge (jrut) Date: 2003-02-25 18:56

Message: Logged In: YES user_id=720847

Additional info -- the site.py used in Python 2.2.2 explicitly removes non-existing and non-directory files from sys.path.

The Python 2.3 site.py does not have that feature.

----------------------------------------------------------------------