Mmm, we solved half of the cause of this one.
Test runs are kicked off via setuptools's test command. But this
happens programmatically, and successively in one process. But
setuptools's test command clears all modules imported during a test
run from sys.modules - hence it is intended that module
Hi Scott, Diez,
On May 8, 8:21 pm, Scott David Daniels wrote:
> Diez B. Roggisch wrote:
> > Try putting an "import pdb; pdb.set_trace()" on top of the decimal module.
[snip]
> You can also run Python with the "-v" or "-vv" flags to get output
> about exactly what files are getting imported from t
Diez B. Roggisch wrote:
Iwan Vosloo wrote:
We have a rather complicated program which does a bit of os.chdir and
sys.path manipulations. In between all of this, it imports the decimal
module several times
However, it imports a new instance of decimal sometimes. (Which is a
problem, since a
Iwan Vosloo wrote:
> Hi there,
>
> We have a rather complicated program which does a bit of os.chdir and
> sys.path manipulations. In between all of this, it imports the decimal
> module several times.
>
> However, it imports a new instance of decimal sometimes. (Which is a
> problem, since a
Hi there,
We have a rather complicated program which does a bit of os.chdir and
sys.path manipulations. In between all of this, it imports the decimal
module several times.
However, it imports a new instance of decimal sometimes. (Which is a
problem, since a decimal.Decimal (imported at point A
