Import This: the Tenth International Python Conference
Andrew Kucheling won O'Reilly's Frank Willison award for the most outstanding contributions to the Python community. He won it for his work on the crypto toolkit, HOWTOs and his "What's New in Python 2.2" series. He had a proud smile on his face when he accepted the award. (Frank Willison was a late editor at O'Reilly and a big Python supporter.)
We shared the foyer and ballrooms with a group of US Marines. There's a definite irony in the contrast between the spiffily dressed Marines in uniform and the scruffily dressed geeks, although I'm not sure what it is. One Pythoneer commented that if you got a hundred Python attendees against four Marines, it would be a fair fight. But if the activity were information warfare, the ratio would be reversed.
David Ascher during the closing ceremony gave the funniest quote of the conference: "I used to be uptight about garbage collection, but then I realized that the Web has no garbage collection."
There was nothing like Toilet Paper this year.
Many thanks to to the conference sponsors for supporting Python even in this difficult economic climate:
Hostway (a web hosting company that uses Python internally, including the control panel application for customers to modify their account information on-line)
Archaeopteryx Software (maker of Wing IDE)
Python and Zope Job Market (a place to trade resumés and jobs)
Rubicon Research (health care software)
Zope (they employ PythonLabs now)
O'Reilly (you know what they publish)
The economy brings up another issue: the cost of the conference. $545 (or $840 with Developers' Day) is too steep for most individuals and even for many companies. I know at least three people in my local Python group who would have attended if they could afford it, and I'm sure others can say the same thing. This is especially important for an open-source project, because enthusiastic Pythoneers are the lifeblood of the project, and when they can't participate in something, the whole project suffers. Nevertheless, the fact remains that even the current price is not enough for the conference to break even, and if it weren't for the sponsors there would be no conference. Finding affordable meeting space for three hundred people is a difficult task, and it won't get any easier. (Maybe Zope, Inc. can buy a hotel and call it the Zope Hotel?) So, I wonder if the Python community can put their heads together and come up with a different kind of conference, or something other than a conference, that all enthusiastic Pythoneers can participate in. Perhaps a set of regional meetings rather than one international conference? I don't know what. Certainly, everybody wants to hear Guido speak, and Guido can't go to ten different regional meetings. Maybe we can webcast his talks and other important Python talks (with transcripts for the multimedia-impaired), so that more people can bridge the distance+cost barrier. A call-in radio talk show called "The Python Hour"? Farfetched, but the more we brainstorm ideas, the more we'll come up with something practical.
Next year will bring another round of maturing for Python and Zope and spin-off products from Zope and packages that have recently been released or are still on the drawing boards. What will they look like? All we know is what the Monty Python announcer says, "And now for something completely different...."
Mike Orr is part of the tech staff at SSC, Inc. and Editor of Linux Gazette.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Stunnel Security for Oracle
- Tech Tip: Really Simple HTTP Server with Python
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide