[issue23097] unittest can unnecessarily modify sys.path (and with the wrong case)

Charlie Dyson added the comment: As an aside, should that be sys.path.insert(1, X)? As 0 has a special meaning (I've often thought this is a slightly odd convention). Another aside: I noticed this because I was looking to write a module finder, and thought I could extract one out of this

[issue23097] unittest can unnecessarily modify sys.path (and with the wrong case)

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23097] unittest can unnecessarily modify sys.path (and with the wrong case)

Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: +michael.foord ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23097 ___ ___

[issue23097] unittest can unnecessarily modify sys.path (and with the wrong case)

New submission from Chris Jerdonek: I have observed that when running unit tests using unittest's test discovery, unittest can simultaneously (1) modify sys.path unnecessarily (by adding a path that is already in sys.path with a different case), and (2) modify sys.path by adding a path of the