Modify ↓
Opened 17 years ago
Closed 6 years ago
#7142 closed enhancement (wontfix)
Set pkg_resources extraction path manually
| Reported by: | Noah Kantrowitz | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | devel |
| Severity: | normal | Keywords: | PYTHON_EGG_CACHE |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
We should use pkg_resources.set_extraction_path instead of requiring PYTHON_EGG_CACHE to be set in the environment. This would allow moving this setting into trac.ini. On a related note, it would be nice to set a saner default than ~/.python-eggs, perhaps to tempfile.gettempdir().
Attachments (0)
Change History (5)
comment:1 by , 14 years ago
comment:2 by , 10 years ago
| Owner: | removed |
|---|
comment:3 by , 6 years ago
| Keywords: | PYTHON_EGG_CACHE added |
|---|
comment:4 by , 6 years ago
I suggest closing as wontfix.
If Trac is installed as a egg file, only PYTHON_EGG_CACHE environment can specify extraction path (comment:1).
Also, if TRAC_ENV_PARENT_DIR (multi-project) is used, the extraction path is shared between all Trac environments. After moving the setting to trac.ini, same value must be configured in all trac.ini. That's redundant.
comment:5 by , 6 years ago
| Milestone: | next-major-releases |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Doesn't the extraction path need to be set prior to entering Trac code if Trac is installed as an egg? Then again,
PYTHON_EGG_CACHE(and related directives) seem to be working well these days.