search

PiRSquared17 / cing

Automatically exported from code.google.com/p/cing
0 stars 0 forks source link

Clean-up NTutils #162

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
NTutils has a number of rudiments/imports to clean to isolated the code better:

- ROGscore class should be in cing.core.classes
  This will remove the red, green and orange import

- NaNstring should be defined in cing.Libs.fpconst

- verbosityDetail, verbosityDebug, etc should not be defined in cing, but
in NTutils where they are 'implemented' in the IO routines

with these changes, NTutils only imports from Libs or general python Libs

Original issue reported on code.google.com by g.vuis...@gmail.com on 21 Apr 2009 at 6:40

GoogleCodeExporter commented 9 years ago 
Actually, I now see that NaNstring should be defined in cing.Libs.NTutils as 
well,
since it is used in val2str,

Original comment by g.vuis...@gmail.com on 21 Apr 2009 at 10:02

GoogleCodeExporter commented 9 years ago

Original comment by g.vuis...@gmail.com on 21 Apr 2009 at 10:04

GoogleCodeExporter commented 9 years ago 
The classes in cing.Libs and cing.core are delicately balanced to prevent 
cyclic deps. Simply moving ROGscore to cing.core.classes.py failed when I tried 
a couple of scenarios. For the time, I gave the ROGscore class it's own 
module which always works but is less concise.

Committed in r564. I'll await raising this issue's priority before addressing 
the other points.

Original comment by jurge...@gmail.com on 22 Apr 2009 at 7:53

GoogleCodeExporter commented 9 years ago

Original comment by jurge...@gmail.com on 27 May 2009 at 11:50