Hi there,
Rick McGuire wrote:
You have misunderstood what this thread was about. Mike's programs
were unaffected, oodialog has already been reworked to remove an old
hacky way to get around the old behavior. This really only becomes an
issue for programs that stuffed things into .local to
Sorry, I am adamantly opposed to any effort to preserve that old
behavior. It was the cause of no end of problems, including most of
the hacks you're now citing as instances of the problems. At this
point in the project, what you're proposing will be an incredibly
disruptive change to the code
Rick McGuire wrote:
Sorry, I am adamantly opposed to any effort to preserve that old
behavior. It was the cause of no end of problems, including most of
the hacks you're now citing as instances of the problems. At this
point in the project, what you're proposing will be an incredibly
Ok, I've come up with a compromise. Packages are still loaded and
maintained on a process basis, but each interpreter instance will
maintain a list of packages that is used by code running in the
instance and will ensure that the prologue code gets run when the
package is first requested by the
Rick McGuire wrote:
Ok, I've come up with a compromise. Packages are still loaded and
maintained on a process basis, but each interpreter instance will
maintain a list of packages that is used by code running in the
instance and will ensure that the prologue code gets run when the
package is
