Opened 17 years ago

Closed 13 years ago

#996 enhancement closed invalid (invalid)

t.plugin caching and read-only package directories

Reported by: mg Owned by:
Priority: normal Milestone:
Component: core Keywords:
Cc: Cory Dodt, radix, Jean-Paul Calderone, symbiont, mg Branch:
Author:

Description


Change History (12)

comment:1 Changed 17 years ago by mg

t.plugin writes the dropin.cache to the package's directory. However, it's not
uncommon for that directory to be read only, i.e. when Twisted is installed to
site-packages but all the Twisted apps run as a non-root user. Perhaps t.plugin
should cache in memory instead or as well writing to the package dir?

comment:2 Changed 17 years ago by Jean-Paul Calderone

It is intended that the install process write the cache files.

comment:3 Changed 17 years ago by Cory Dodt

Would someone explain how this works?

comment:4 Changed 17 years ago by mg

Searching for any type of plugin in a package is enough to write the
dropin.cache to the package directory. It should be enough to load up Twisted's
IServiceMaker plugins once Twisted has been installed.

I'm not sure of the correct way to load IServiceMaker plugins but
twisted.scripts.mktap.loadPlugins() looks like a reasonable choice. However:

  * Are there any other Twisted plugin types that need loading at
    installation time that moonfallen and radix should know about?
  * What about other packages/applications that provide/use plugins? Should
    they be catered for better?

comment:5 Changed 17 years ago by Cory Dodt

Committed r13679.

comment:6 Changed 17 years ago by Jean-Paul Calderone

Yay Windows.

Anyone feel like getting the other installers (bare setup.py, .dpkg, .rpm?) to
do this, too?

comment:7 Changed 16 years ago by mg

Cross referencing to issue 1126 "Packge Twisted using Eggs/EasyInstall" because
they probably affect each other.

comment:8 Changed 14 years ago by Jean-Paul Calderone

Owner: changed from Jean-Paul Calderone to radix

This seems release related, basically. I might do some work on this, but someone should clarify what the remaining work to be done is.

comment:9 Changed 13 years ago by zooko

#2406 is a ticket about how to handle the warnings that result when this directory isn't writable when we're attempting to update the cache file.

By the way, this is a headache for me because setuptools/easy_install don't have a method of executing arbitrary code after install -- post-install hooks. So I'm kind of hoping that this somehow goes away. Maybe mg's suggestion of using RAM for the cache should be reconsidered -- it would go a lot faster in some cases...

comment:10 Changed 13 years ago by Glyph

Zooko meant #2409.

comment:11 Changed 13 years ago by Glyph

Resolution: invalid
Status: newclosed

OK, so, after thinking about this a bit, this ticket doesn't really describe any course of action, just notes a potential issue. I think that #2409 is a much more useful ticket related to that issue, so I'm going to close this one as invalid since I have no idea how this is actionable any more.

comment:12 Changed 11 years ago by <automation>

Owner: radix deleted
Note: See TracTickets for help on using tickets.