Re: EOFError: marshal data too short -- causes?

From	Glenn Linderman <v+python@g.nevcal.com>
Newsgroups	comp.lang.python
Subject	Re: EOFError: marshal data too short -- causes?
Date	2015-12-30 12:35 -0800
Message-ID	<mailman.84.1451508137.11925.python-list@python.org> (permalink)
References	<56822D4F.8070309@g.nevcal.com> <n5tc6o$dgl$1@ger.gmane.org> <56823DBC.9010205@g.nevcal.com> <20151229085625.036f548d@imp>

Show all headers | View raw

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 comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: EOFError: marshal data too short -- causes? Glenn Linderman <v+python@g.nevcal.com> - 2015-12-30 12:35 -0800

csiph-web