On 1/7/2016 7:44 PM, Dennis Lee Bieber wrote:
On Thu, 7 Jan 2016 10:55:38 -0800, Glenn Linderman
declaimed the following:
But all the touched files are .pyc files (and the directories
__pycache__ directories). None of the source files were modified. So
why would any
On 12/29/2015 5:56 AM, D'Arcy J.M. Cain wrote:
On Tue, 29 Dec 2015 00:01:00 -0800
Glenn Linderman wrote:
OK, so I actually renamed it instead of zapping it. Them, actually,
Really, just zap them. They are object code. Even if you zap a
perfectly good .pyc file a
On 12/29/2015 1:00 PM, Terry Reedy wrote:
I updated to 2.7.11, 3.4.4, and 3.5.1 a couple of weeks ago, so the
timestamps are all fresh. So I don't know what happened with 3.4.3
timestamps from last April and whether Windows itself touches the
files. I just tried importing a few and Python
On 12/29/2015 3:01 AM, Glenn Linderman wrote:
Now the __pycache__ directory is full of .pyc and .pyo files (from the
install?
The installer optionally runs compileall on /Lib and recursively on its
subpackages. The option defaults to 'yes', at least for 'install for
everyone', as writing
On 12/28/2015 11:19 PM, Terry Reedy wrote:
On 12/29/2015 1:50 AM, Glenn Linderman wrote:
Here's a sanatized stack trace off my web server:
File ".../cgihelpers.py", line 10, in
import cgitb
File ".../py34/lib/python3.4/cgitb.py", line 24, in
import inspect
File
On Tue, 29 Dec 2015 00:01:00 -0800
Glenn Linderman wrote:
> OK, so I actually renamed it instead of zapping it. Them, actually,
Really, just zap them. They are object code. Even if you zap a
perfectly good .pyc file a perfectly good one will be re-created as
soon as
On 12/29/2015 1:50 AM, Glenn Linderman wrote:
Here's a sanatized stack trace off my web server:
File ".../cgihelpers.py", line 10, in
import cgitb
File ".../py34/lib/python3.4/cgitb.py", line 24, in
import inspect
File ".../py34/lib/python3.4/inspect.py", line 54, in