Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #101011 > unrolled thread
| Started by | Glenn Linderman <v+python@g.nevcal.com> |
|---|---|
| First post | 2015-12-30 12:35 -0800 |
| Last post | 2015-12-30 12:35 -0800 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: EOFError: marshal data too short -- causes? Glenn Linderman <v+python@g.nevcal.com> - 2015-12-30 12:35 -0800
| From | Glenn Linderman <v+python@g.nevcal.com> |
|---|---|
| Date | 2015-12-30 12:35 -0800 |
| Subject | Re: EOFError: marshal data too short -- causes? |
| Message-ID | <mailman.84.1451508137.11925.python-list@python.org> |
On 12/29/2015 5:56 AM, D'Arcy J.M. Cain wrote: > On Tue, 29 Dec 2015 00:01:00 -0800 > Glenn Linderman <v+python@g.nevcal.com> 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 you import it. No need to clutter up you file system. > Yes, the only value would be if the type of corruption could be determined from the content.
Back to top | Article view | comp.lang.python
csiph-web