Author barry
Recipients Anthony Sottile, Chris Billington, Ethan Smith, Ivan.Pozdeev, SilentGhost, __Vano, barry, brett.cannon, cheryl.sabella, christian.heimes, eric.smith, eric.snow, ionelmc, jaraco, mhammond, ncoghlan, pitrou, steve.dower, takluyver, terry.reedy, veky
Date 2019-02-26.23:41:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <BA549579-338D-49EA-8FE9-165C958E0CFA@python.org>
In-reply-to <23826c7b-edc9-ca4b-866b-afdf0bb640b4@mail.ru>
Content
On Feb 26, 2019, at 13:23, Ivan Pozdeev <report@bugs.python.org> wrote:
> 
> Easy. Insert a chunk into site.py that would call pdb.set_trace() if an envvar (e.g. `PYSITEDEBUG') or a command line switch is set.
> 
> Actually, why can't whoever has this problem add such a chunk themselves? Is this really such a frequent and ubiquitous problem
> that this needs to be in the stock codebase? I suspect we're dealing with a vocal minority here.

Basically yes, I’ve done this.  But think of the poor user who doesn’t have that expertise or ability to hack on an installed Python’s site.py file.  When their application breaks because some faulty pth was installed behind their back, how do they debug their application when the breakage has already occurred before Python even gets to their code?  How do they answer questions like “where did that magical sys.path entry come from?” or “how did that module get in sys.modules already?”
History
Date User Action Args
2019-02-26 23:41:20barrysetrecipients: + barry, mhammond, brett.cannon, terry.reedy, jaraco, ncoghlan, pitrou, eric.smith, christian.heimes, ionelmc, SilentGhost, __Vano, eric.snow, takluyver, steve.dower, veky, Ivan.Pozdeev, Anthony Sottile, Ethan Smith, cheryl.sabella, Chris Billington
2019-02-26 23:41:20barrylinkissue33944 messages
2019-02-26 23:41:20barrycreate