So this isn't actually a problem, because our scripts all do 'import _pythonpath' which resets the path correctly. Well... almost all of our scripts do. Some of the scripts in database/schema are so old they don't use this mechanism and cause warnings to be raised about module conflicts.
So this isn't actually a problem, because our scripts all do 'import _pythonpath' which resets the path correctly. Well... almost all of our scripts do. Some of the scripts in database/schema are so old they don't use this mechanism and cause warnings to be raised about module conflicts.