Gabor, On a similar note, it would be helpful to provide a concrete example.
Unlike Java NARs, Python Processors do not have the same concept of multiple layers of parent class loaders right now. Virtual environments provide dependency sharing, but there isn't the same concept of sharing dependencies. Attempting to implement something similar to NAR hierarchy for Python Processors presents some important questions that would have to be addressed. Having a concrete example where to consider these complexities would be a helpful way to evaluate whether it makes sense to introduce additional dependency loading concepts for Python. Regards, David Handermann On Tue, Sep 24, 2024 at 9:41 AM Joe Witt <joe.w...@gmail.com> wrote: > > Gabor > > Can you please describe a specific case or cases where ProcessorA and > ProcessorB should be in the same package/module and yet have such vastly > different (100s of MB or even GB) of dependency requirements? > > Thanks > Joe > > On Tue, Sep 24, 2024 at 7:32 AM Ferenc Gerlits <fgerl...@apache.org> wrote: > > > Hi Gabor, > > > > I like this approach, and I think the restriction you propose (that > > all utility files in the package use the same dependencies, and extra > > dependencies for processor A are only used in ProcessorA.py) is > > reasonable. I would be happy to implement this if there are no > > objections. > > > > Thanks, > > Ferenc > >
