159394 – use of compiled Python files

Bug 159394 - use of compiled Python files

Summary: use of compiled Python files

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Interface (emerge) (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2006-12-29 10:24 UTC by Jerome
Modified:	2006-12-31 08:38 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jerome 2006-12-29 10:24:37 UTC

I ran a "locate emerge" and I could not find something like "emerge.pyc" or "emerge.pyo" python cache files.

Enabling python cached files could speedup portage execution.

Comment 1 Andrew Gaffney (RETIRED) gentoo-dev

2006-12-29 10:39:17 UTC

agaffney@kagome ~ $ find /usr/lib/portage/pym/ -name '*.py[co]'
/usr/lib/portage/pym/portage.pyo
/usr/lib/portage/pym/portage_mail.pyo
/usr/lib/portage/pym/cvstree.pyo
/usr/lib/portage/pym/xpak.pyo
/usr/lib/portage/pym/getbinpkg.pyo
/usr/lib/portage/pym/output.pyo
/usr/lib/portage/pym/portage_util.pyo
/usr/lib/portage/pym/portage_const.pyo
/usr/lib/portage/pym/portage_exception.pyo
/usr/lib/portage/pym/portage_dep.pyo
/usr/lib/portage/pym/portage_versions.pyo
/usr/lib/portage/pym/portage_data.pyo
/usr/lib/portage/pym/portage_manifest.pyo
/usr/lib/portage/pym/portage_checksum.pyo
/usr/lib/portage/pym/portage_exec.pyo
/usr/lib/portage/pym/portage_locks.pyo
/usr/lib/portage/pym/portage_localization.pyo
/usr/lib/portage/pym/xpak.pyc
/usr/lib/portage/pym/portage_gpg.pyo
/usr/lib/portage/pym/eclass_cache.pyo
/usr/lib/portage/pym/portage_update.pyo
/usr/lib/portage/pym/portage_selinux.pyo
/usr/lib/portage/pym/emergehelp.pyo
/usr/lib/portage/pym/cache/__init__.pyo
/usr/lib/portage/pym/cache/cache_errors.pyo
/usr/lib/portage/pym/cache/metadata.pyo
/usr/lib/portage/pym/cache/flat_hash.pyo
/usr/lib/portage/pym/cache/template.pyo
/usr/lib/portage/pym/cache/mappings.pyo
/usr/lib/portage/pym/cache/fs_template.pyo
/usr/lib/portage/pym/cache/metadata_overlay.pyo
/usr/lib/portage/pym/elog_modules/__init__.pyo
/usr/lib/portage/pym/elog_modules/mod_save.pyo
/usr/lib/portage/pym/elog_modules/mod_mail.pyo

agaffney@kagome /usr/lib/portage/bin $ head -n 1 /usr/lib/portage/bin/emerge
#!/usr/bin/python -O

Comment 2 Jerome 2006-12-29 11:01:45 UTC

Yes, but "emerge.py" script is not cached (no "emerge.pyc" or "emerge.pyo").

Comment 3 Zac Medico gentoo-dev

2006-12-29 11:22:47 UTC

(In reply to comment #0)
> Enabling python cached files could speedup portage execution.

It only slightly speeds up the initial launch.  After that, there is no difference.  The time it takes to compile emerge is quite negligible in comparison to all the other things that emerge and the portage libraries do.

Comment 4 Marius Mauch (RETIRED) gentoo-dev

2006-12-31 08:38:40 UTC

(In reply to comment #2)
> Yes, but "emerge.py" script is not cached (no "emerge.pyc" or "emerge.pyo").
> 

What emerge.py script?