Thanks for your help Simon, I've found the issue to be related to mixed
source imports and duplicate paths set in eclipse, which both lead to a
double import situation;
again thanks for the useful links.
--
Marcin
2015-03-02 13:19 GMT+01:00 Simon King si...@simonking.org.uk:
Hi Martin,
On Sun, Mar 01, 2015 at 01:53:30PM +0100, Julien Cigar wrote:
On Fri, Feb 27, 2015 at 11:38:05PM -0500, Michael Bayer wrote:
On Feb 26, 2015, at 5:56 AM, Julien Cigar jci...@ulb.ac.be wrote:
On Wed, Feb 25, 2015 at 06:10:55PM -0500, Michael Bayer wrote:
Julien Cigar
Hi Martin,
Normally, Python caches modules after they are imported, so when you
import a module for the second time it doesn't actually execute the
code again. If you have 3 modules, one, two and common, and
one and two both import common, common should only be loaded
once.
However, there are a
Hi Simon, definitely multiple imports is the issue here, however I don't
know how to get rid of it,
let's say I have a module which i named ormstuff inside it I have a class
named mybase, I do have 2 other modules which
are using this class, and to do so I import it in both places. Now this
might
Hello, I've been busy writing an application which now has grown
considerably, it spans across several packages/modules totalling 200K lines
of python code.
Recently I made some changes to the structure and decided to split several
classes into separate modules for greater flexibility; the
On Mon, Mar 2, 2015 at 11:29 AM, Martino Io martino8...@gmail.com wrote:
Hello, I've been busy writing an application which now has grown
considerably, it spans across several packages/modules totalling 200K lines
of python code.
Recently I made some changes to the structure and decided to
Jonathon Nelson jdnel...@dyn.com wrote:
For a variety of reasons, sometimes it's nice to be able to do something like
this:
with dbsess.begin(rollback=True):
do_stuff
Where the expected behavior is that everything in the context runs in a
transaction, but upon exiting the context
For a variety of reasons, sometimes it's nice to be able to do something
like this:
with dbsess.begin(rollback=True):
do_stuff
Where the expected behavior is that everything in the context runs in a
transaction, but upon exiting the context we issue a rollback. Sometimes
this is useful to
Julien Cigar jci...@ulb.ac.be wrote:
On Sun, Mar 01, 2015 at 01:53:30PM +0100, Julien Cigar wrote:
On Fri, Feb 27, 2015 at 11:38:05PM -0500, Michael Bayer wrote:
On Feb 26, 2015, at 5:56 AM, Julien Cigar jci...@ulb.ac.be wrote:
On Wed, Feb 25, 2015 at 06:10:55PM -0500, Michael Bayer