Re: [Twisted-Python] different import paths lead to insecureJelly

2014-01-03 Thread Glyph
On Jan 2, 2014, at 3:37 AM, exar...@twistedmatrix.com wrote: > Always refer to modules in the same way. Never use relative imports. Explicit relative imports preserve the benefit of being able to re-name your packages without editing every file inside them, but will still give you errors rath

Re: [Twisted-Python] different import paths lead to insecureJelly

2014-01-02 Thread exarkun
On 07:54 am, sank.dan...@gmail.com wrote: I have a project in which various modules need to import a particular module "util" which has the following content: # util.py class FooMaster(pb.Cacheable): ... class FooSlave(pb.RemoteCache): ... pb.setUnjellyableForClass(Fo