"Iwan Vosloo" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> I know my foreign (to python) one class per module idea is what makes
> life more difficult for me here. And there is an argument to be made
> out that it is a stupid remnant I stick to from having used it in other
> pr
I know my foreign (to python) one class per module idea is what makes
life more difficult for me here. And there is an argument to be made
out that it is a stupid remnant I stick to from having used it in other
programming languages (do I have to admit C++ in my background?) Two
small examples o
I know my foreign (to python) one class per module idea is what makes
life more difficult for me here. And there is an argument to be made
out that it is a stupid remnant I stick to from having used it in other
programming languages (do I have to admit C++ in my background?) Two
small examples o
[EMAIL PROTECTED] wrote:
> I'm busy with a large application and feel it would eas my work if I
> can specify dependencies on the granularity of packages, rather than
> modules and classes. Eg:
>
> - By convention I do the one class per file thing. SO in python this
> means one class per module
Hello,
I'm busy with a large application and feel it would eas my work if I
can specify dependencies on the granularity of packages, rather than
modules and classes. Eg:
- By convention I do the one class per file thing. SO in python this
means one class per module - naming classes after their
