Ian Ward's email:
first name at this domain
wardi on OFTC, freenode and github
Python is a wonderful language, but some parts should really have bright WARNING signs all over them. There are features that just can't be used safely and others are that are useful but people tend to use in the wrong ways.
This is a rough transcript of the talk I gave at my local Python group on November 15, with some of the audience feed back mixed in. Most of this came from hanging around the Python IRC channel, something I highly recommend.
[update 2011-12-19: improved "array" critique, add "python -i" suggestion to "reload" critique, add html targets to sections]
[update 2011-12-20: include additional links from agentultra and ffrinch]
[update 2012-01-06: added hasattr and find]
[update 2012-04-09: some links and syntax highlighting]
This release adds the long-requested linear scale feature to Speedometer. You can now also adjust the minimum and maximum values displayed, and switch all units shown to bits per second.
Urwid maintenance releases 1.0.1 and 0.9.9.3 are now available. This may be the last 0.9.9 release, users are strongly encouraged to upgrade.
This is a major feature release for Urwid.
Happy 1.0 Urwid! It's been a great nearly-seven years since our first release. Huge thanks to everyone that's contributed code, docs, bug reports and help on the mailing list and IRC.
In any web application user data must be translated from HTML form data to native types and database types, and back again. Django web applcations are no different.
The "right way" to handle custom types is to extend Django's widgets, form fields and model fields. However, understanding exactly how these types perform each step of the conversion can be confusing. This post will attempt to explain how the data is converted at each stage and offer some advice about creating custom widgets, form fields and model fields.
This article is based on Django 1.3 and assumes the reader has experience creating and using Django forms, models and validation.
The third iteration the Arevco Lighting web site is now up.
The old site was simple HTML and images generated from a script, which I quite liked but wasn't the easiest thing for other people to update. The new site has been professionally skinned and is now running a Django CMS with some custom index code for product pages. I used the following:
I've used Gerbi now for a few public web sites. It's a well designed and usable CMS that is quite easy to extend. It also has good multilingual support that will make translating content as easy as editing the pages.
I set up a VM to present software to a client remotely, but I needed a way to record both the audio in and out so that I could capture both my presentation and the client's questions. In the past I've used some ALSA configuration magic for audio things advanced enough that they don't have a friendly GUI, but since Pulse Audio is the shiny new thing I decided to go that route.
It turns out to be fairly simple. I create a new null sink (think: fake sound card for output) and attach a loopback from the audio out monitor of the "real" sound card and another from the the audio in of the "real" sound card:
pactl load-module module-null-sink sink_name=bothsides pactl load-module module-loopback latency_msec=5 sink=bothsides \ source=alsa_output.pci-0000_00_04.0.analog-stereo.monitor pactl load-module module-loopback latency_msec=5 sink=bothsides
alsa_output... source comes from running
pactl list and copying the device name. The second loopback automatically uses the only
alsa_input... source device. Then I can record from the monitor of this null sink with a command like:
pacat --record -d 2 | sox -t raw -r 44100 -s -L -b 16 -c2 - "recording.wav"
-d 2 option selects the new null sink monitor device I created (the index may be different in your case). Last, you may want to use the
pavucontrol program to adjust the levels for the input and output so you don't end up with one sounding much louder than the other in the combined recording.
« page 1 2 3 4 5 6 7 … 10 11 12 page »