Daniel & Oleg,
> > creating one .py file for each class, but it's turning out to be a mess
> > of include statements.
>
>He-he, Python is not Java!
I was anticipating this response, but I did have good intentions when we set
out. We are working on an application that will validate and exp
On 11 December 2011 17:22, Daniel Fetchinson wrote:
> > I need help managing my project files. I've got over 120 class files
> > each that have their own specific validation routines. Most of which
> > are pretty tame, but some are pretty nasty. Anyways, I took a stab at a
> > creating one .py
> I need help managing my project files. I've got over 120 class files
> each that have their own specific validation routines. Most of which
> are pretty tame, but some are pretty nasty. Anyways, I took a stab at a
> creating one .py file for each class, but it's turning out to be a mess
> of i
Hi!
On Sat, Dec 10, 2011 at 02:47:44PM -0800, Glenn Rutkowski wrote:
> creating one .py file for each class, but it's turning out to be a mess
> of include statements.
He-he, Python is not Java!
> Going back to a single file makes for a HUGE
> file which is manageable, but annoying when sea
I need help managing my project files. I've got over 120 class files
each that have their own specific validation routines. Most of which
are pretty tame, but some are pretty nasty. Anyways, I took a stab at a
creating one .py file for each class, but it's turning out to be a mess
of includ
