On Sep 9, 1:04 am, xkenneth [EMAIL PROTECTED] wrote:
On Sep 8, 3:35 pm, David [EMAIL PROTECTED] wrote:
How do import statements that are declared at the top of a python
module work?
http://docs.python.org/tut/node8.html
On Sat, 08 Sep 2007 12:42:19 -0700, xkenneth wrote:
How do import
xkenneth a écrit :
Ah, yes, a couple of things:
- avoid the 'one-class-per-file' syndrom. It's perfectly ok to have tens
Yes but i find it hard to edit classes easily when I have more than
one class per file.
Why so ? Could it be that your classes are growing too fat ?
--
xkenneth a écrit :
On Sep 7, 2:04 pm, Wildemar Wildenburger
[EMAIL PROTECTED] wrote:
Paul Rudin wrote:
xkenneth [EMAIL PROTECTED] writes:
Ah, yes, a couple of things:
- avoid the 'one-class-per-file' syndrom. It's perfectly ok to have tens
Yes but i find it hard to edit classes easily when
On Sep 7, 2:04 pm, Wildemar Wildenburger
[EMAIL PROTECTED] wrote:
Paul Rudin wrote:
xkenneth [EMAIL PROTECTED] writes:
Ah, yes, a couple of things:
- avoid the 'one-class-per-file' syndrom. It's perfectly ok to have tens
Yes but i find it hard to edit classes easily when I have more than
On Sat, 08 Sep 2007 12:42:19 -0700, xkenneth wrote:
How do import statements that are declared at the top of a python
module work?
They import the module. ;-)
for instance
from MyModule.Objects import *
class Class:
def function:
#here i cannot access the things
How do import statements that are declared at the top of a python
module work?
for instance
from MyModule.Objects import *
class Class:
def function:
#here i cannot access the things that should have been
imported from the above statement
#i printed the
How do import statements that are declared at the top of a python
module work?
http://docs.python.org/tut/node8.html
--
http://mail.python.org/mailman/listinfo/python-list
On Sep 8, 3:35 pm, David [EMAIL PROTECTED] wrote:
How do import statements that are declared at the top of a python
module work?
http://docs.python.org/tut/node8.html
On Sat, 08 Sep 2007 12:42:19 -0700, xkenneth wrote:
How do import statements that are declared at the top of a python
On Sep 8, 2007, at 8:04 PM, xkenneth wrote:
Code doesn't compile in python. This is pseudo code anyways.
Can't post actual code and tracebacks because the code is proprietary.
MyModule is pseudo code, and i forgot the arguments, the actual code
and errors are unimportant for this question.
xkenneth a écrit :
All,
I apologize if this is a commonly asked question, but I didn't
find anything that answered my question while searching.
So what I have right now is a few packages that contain some commonly
used functions and another package that contains all of my custom
All,
I apologize if this is a commonly asked question, but I didn't
find anything that answered my question while searching.
So what I have right now is a few packages that contain some commonly
used functions and another package that contains all of my custom
error classes. I want these
xkenneth [EMAIL PROTECTED] writes:
Ah, yes, a couple of things:
- avoid the 'one-class-per-file' syndrom. It's perfectly ok to have tens
Yes but i find it hard to edit classes easily when I have more than
one class per file.
Why?
--
http://mail.python.org/mailman/listinfo/python-list
Ah, yes, a couple of things:
- avoid the 'one-class-per-file' syndrom. It's perfectly ok to have tens
Yes but i find it hard to edit classes easily when I have more than
one class per file.
Regards,
Ken
--
http://mail.python.org/mailman/listinfo/python-list
Paul Rudin wrote:
xkenneth [EMAIL PROTECTED] writes:
Ah, yes, a couple of things:
- avoid the 'one-class-per-file' syndrom. It's perfectly ok to have tens
Yes but i find it hard to edit classes easily when I have more than
one class per file.
Why?
Scroll-Blindness would be a good reason.
14 matches
Mail list logo
