Prev: long int computations
Next: duplicate temporary file?
From: Trent Nelson on 6 May 2010 21:20
> I'm interested in improving my python design by studying a large,
> well-designed codebase.

I'll tell you one of the best ways to improve your Python code: attend
one of Raymond Hettinger's Code Clinic workshops at a Python conference
and put some up of your work up on the projector for 20+ developers to
rip apart, line by line ;-) You'll pick up more in 30 minutes than you
ever thought possible.

Trent.

From: TomF on 6 May 2010 22:48
On 2010-05-06 18:20:02 -0700, Trent Nelson said:
>> I'm interested in improving my python design by studying a large,
>> well-designed codebase.
>
> I'll tell you one of the best ways to improve your Python code: attend
> one of Raymond Hettinger's Code Clinic workshops at a Python conference
> and put some up of your work up on the projector for 20+ developers to
> rip apart, line by line ;-) You'll pick up more in 30 minutes than you
> ever thought possible.

I don't doubt it. But I'm not really interested in line (micro) level
code issues at the moment. Not that my code couldn't stand being
improved, but I'm more interested in seeing how medium/large OO python
systems are designed. If I could get this from a book I would, but I
suspect I need to study real code.

-Tom

From: Aahz on 7 May 2010 08:23
In article <2010050619481239450-tomfsessile(a)gmailcom>,
TomF <tomf.sessile(a)gmail.com> wrote:
>
>I don't doubt it. But I'm not really interested in line (micro) level
>code issues at the moment. Not that my code couldn't stand being
>improved, but I'm more interested in seeing how medium/large OO python
>systems are designed. If I could get this from a book I would, but I
>suspect I need to study real code.

My suspicion is that very very few medium/large systems are truly
"well-designed". I've had occasion to dive into the CherryPy and Cheetah
code, you might look there.
--
Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/

"It is easier to optimize correct code than to correct optimized code."
--Bill Harlan
From: Paul Kölle on 9 May 2010 16:50
Am 07.05.2010 04:48, schrieb TomF:
> On 2010-05-06 18:20:02 -0700, Trent Nelson said:
>>> I'm interested in improving my python design by studying a large,
>>> well-designed codebase.
>>
>> I'll tell you one of the best ways to improve your Python code: attend
>> one of Raymond Hettinger's Code Clinic workshops at a Python conference
>> and put some up of your work up on the projector for 20+ developers to
>> rip apart, line by line ;-) You'll pick up more in 30 minutes than you
>> ever thought possible.
>
> I don't doubt it. But I'm not really interested in line (micro) level
> code issues at the moment. Not that my code couldn't stand being
> improved, but I'm more interested in seeing how medium/large OO python
> systems are designed. If I could get this from a book I would, but I
> suspect I need to study real code.
Then trac might be a good candidate, start here

http://trac.edgewall.org/wiki/TracDev/ComponentArchitecture

then read

http://trac.edgewall.org/browser/trunk/trac/core.py#latest

there is one rather dubious hack in the implementation of implements()
but I like the conceptual simplicity.

cheers
Paul

From: Lawrence D'Oliveiro on 13 May 2010 08:35
In message <mailman.2704.1273192642.23598.python-list(a)python.org>, MRAB
wrote:

> Albert Hopkins wrote:
>
>> On Thu, 2010-05-06 at 16:38 -0700, Patrick Maupin wrote:
>>
>>> I don't know how this applies to reading other peoples' code, but
>>> recent research shows we learn more from success than failure
>>
>> That's good to learn, because for years I have been intentionally
>> failing in order to learn from it and become successful, and it hasn't
>> really worked out for me :|
>>
> Failure just teaches you what you shouldn't do, not what you should...

But there are more different ways to fail than to succeed, therefore more to
learn.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: long int computations
Next: duplicate temporary file?