Here's the plan for the PyGTA meeting this Tuesday (the 15th).
Bring a piece of code that you love. Something that's elegant, beautiful, efficient, useful, perfectly formatted, meaningful, warped or wonderful in some way. We'll take 5 minutes each and present our chosen piece of code. Then we'll have people ask questions about the code and why you love it.
The code has to be something that can be exposed to the public w/out any non-disclosure agreements or the like, but doesn't necessarily have to be Open Source or distributed. What we're looking for is a discussion of the beauty in the code, the amazing things about it that make it worthwhile. The code does not need to be your own work, nor does it necessarily need to be in Python.
If possible, try to cut down the code you present to a couple of pages (screens) of code, but if your aesthetic preference runs to big systems, be able to describe the system you choose well enough to communicate the wonder of it to the rest of us.
Is there any beautiful code out there? Does beauty in code matter? Is code poetry or just grotty machinery?
BTW: yes, there's a DemoCamp on the 15th as well, but it's already sold out. We're so much cooler anyway...
Comments
2010-07-25 14:02
> and would have no Trac integ ration The trac-bzr plugin[ 1] seems to provide good integ ration between bzr and t [...]
2010-07-13 21:47
I've always been fascinated wi th the Asterisk AMI interface. So much so that I married tha t fascination with the [...]
2010-07-03 21:32
Yes, only references in dicti onaries are replaced, so hold ing references in lists, tuple s, etceteras keeps them alive.
2010-07-03 11:18
They hold references to remove and install?
2010-06-24 08:34
There's higher-level objects w hich are tracking what is repl aced (the actual Mock objects) . They hold references [...]
2010-06-24 08:23
I haven't tried it, but it see ms to me like this approach ha s one fundamental problem: If you replace all refs o [...]
2010-06-24 08:22
That's the "magic" that made m e go "ooh shiny"
2010-06-24 06:03
That's even more evil than the mock patch decorator...
2010-06-06 18:33
blush Oh.
2010-06-06 11:07
That's what the module does (a utomatically), but on a per-te st-run basis, and only for the process being tested (i [...]
2010-06-06 02:43
Maybe I'm missing something im portant here, but why not just write small scripts to mimic whatever dangerous utili [...]
2010-06-05 15:17
I thought about stubbing out t he python call to the process in the current process, but I want something which stu [...]
2010-06-05 14:47
Hmm... if Mock isn't flexibl e enough to handle mocking pro cesses adequately then I'd lik e to know how it could b [...]
2010-05-19 10:27
Hey, maybe it's a stupid new bie question, but where and ho w exactly should the patching of the core take place? [...]
2010-05-04 14:36
I used Qemu and VirtualBox pre tty extensively back when I wa s working for the OLPC, but mo st of the stuff we were [...]