This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author benjamin.peterson
Recipients Mike.Solomon, benjamin.peterson, jcea, nadeem.vawda, vstinner
Date 2011-05-27.03:47:27
SpamBayes Score 0.008462581
Marked as misclassified No
Message-id <BANLkTi=pPcYfxLVXRUFr9+RjhbJe1ig33w@mail.gmail.com>
In-reply-to <BANLkTinpmaLQwWOfxa79s=bEDBsHzGs6wg@mail.gmail.com>
Content
2011/5/26 Mike Solomon <report@bugs.python.org>:
>
> Mike Solomon <msolo@gmail.com> added the comment:
>
> If you have a file with say a hundred functions, and each function contains
> the full path of that file on disk, your pyc file will contain about
> (100*(path_size+overhead)) bytes. In some cases, this is pretty
> significant.

I see. The support for saving interned strings no longer exists in Py3
where this "feature" would have to be added.
History
Date User Action Args
2011-05-27 03:47:28benjamin.petersonsetrecipients: + benjamin.peterson, jcea, vstinner, nadeem.vawda, Mike.Solomon
2011-05-27 03:47:27benjamin.petersonlinkissue12190 messages
2011-05-27 03:47:27benjamin.petersoncreate