Files changed (29)
The `Cioppino Sprint`_ was recently held in Bodega Bay, CA. It was a `beautiful location`_ for a gathering of awesome Plone folks; and much was accomplished. Unfortunately on the second morning of the sprint, we were all deeply saddened to hear about the passing of Dorneles Treméa.
Why? If for no other reason, because it comes from a member of the Python community: Chad Whitacre of http://aspen.io fame. And the Python community has become near and dear to me, second only to my-one-true-open-source-love: Plone. So I want to see open source developers, particularly Python developers, succeed.
People do not understand gittip. Or, they do not understand how I use it. Worse, they **think** they understand it _. So much so, some choose to comment about it publicly.
One of the first things I do on a new system is change my shell to **Zsh** in ``System Preferences -> Users & Groups -> Current User -> Right Click -> Advanced Options...``. Don't forget to ``Click the lock to make changes`` first.
After I take possession of my new laptop (running **Mountain Lion**, the newest OS X at the time of this writing), I head to the App Store to download XCode. _ Among many other things, XCode gives me the GNU C Compiler and allows me to type "gcc" in my ``Applications -> Utilities -> Terminal``.
Now I need a Python interpreter _. For development I use the `Collective Python Buildout <https://github.com/collective/buildout.python>`_ but I also enjoy using `Homebrew's <http://mxcl.github.com/homebrew/>`_ Python 2.7. I use Homebrew for a variety of other things too (e.g. mobile-shell AKA mosh) so here we go::
Which reminds me, don't forget that installing the command line utilities in Mountain Lion's XCode requires an additional step in ``Preferences -> Downloads -> Command Line Tools -> Install``:
*Plone Kitty* is the name of a theme (then called "skin") that shipped with the earliest versions of `Plone <http://plone.org>`_ (1.1 in the image above). This was a simpler time when the web was new, and everything was possible!
Also, I've been subscribing to, reading, and participating in discussions on mailing lists since about the time Mailman 1.0 was released circa 1999 _. And I have fond memories of interacting administratively with MajorDomo and ListServ software. And by administratively, I mean sending the software commands and getting back a response. In fact, you might say I get along better with the software and machines than I do with the humans that use them. Which is not to say that I'm not a people person: I love people. But I do struggle with striking the right balance between hacking machines and communicating with humans.
Chapter 5 is all about "working with file output". For reference, here are some of the images produced by the examples in this chapter (I wrote ``jpg`` files instead of ``png`` files due to a problem with my libpng: `RuntimeError: Could not create write struct <https://www.google.com/#q=RuntimeError%3A+Could+not+create+write+struct&safe=off>`_.)
*This is my entry for Tarek Ziadé's New Year's Python Meme, a tradition I have come to enjoy. Both to reflect on the current year and look back on previous years. So here it is.*
I'm hoping that the Plone team can unify the content editing experience again in Plone 5, possibly via simplifying the "old style" templates such that it's easier to map them to custom Diazo themes.
I think a lot about what other people think about Plone, so I decided this book will feature comments from the general public in it. E.g.:
#. Add a status message to plone.org to indicate a maintenance window is in progress. I chose to customize the ``main_template`` to accomplish this, but ideally we'd have some functionality in Plone that allowed site administrators to easily configure status messages.
#. Disable logins. Since the upgrade takes a long time, we don't want content being edited during this process. I chose to use David Glick's technique of disabling PAS. I moved the ldap authentication plugin to the Active Plugin list, thus disabling PAS such that only ZODB users could login. But ideally we'd have some feature in Plone to allow site administrators to disable logins.
#. Run the upgrade. I forgot to mention earlier something very important: **On plone.org, you can't access Zope from the internet.** And you can't run the upgrade without accessing Zope. Hence run the following command to access the server, then access Plone via ``http://localhost:8080``::
- The `ability to create packages through the web`_ (i.e. from the web browser to GitHub, whereas normally you'd run PasteScript in your Terminal).
Still, we have only scratched the surface of what could potentially be provided to the Python community. Future plans include:
Aspeli correctly addresses one of my biggest pet peeves (concerns) about what I believe to be an **ANTI-PATTERN** in almost every Plone buildout: buildout:eggs (referring to the eggs parameter of the buildout section; it does not exist, other than as a convenient variable setting).
Did you see? You might have missed it. No mention of **Products** WHAT-SO-EVER. "Product" was a term that Zope2 used for Python libraries that enhanced the functionality of Zope2, and it stuck. Now, it should die in favor of a term everyone else in the world is familiar with (in this context): add-on. Well played, Aspeli. Well played.
This release marks the first "serious effort" I have put into Pillow. While I've always enjoyed working on it in my spare time, I knew that there was no way I could finish it in time for PyCon 2013 (as I promised) without getting some financial assistance.
I love to debate issues. The more complex, the better. I have no formal training in `debate`_, but I wish I did. It may have better prepared me to face different personality types with varying degree of communication skill. You don't have to watch the 2012 U.S. Presidential Debates to know that people will say things that are **BATSHIT CRAZY** to make their point. I've done it myself. That's why we need rules to formalize our discussions, because it's hard to stay on point.
This is you: I **use virtualenv all the time and I love it!** But I hate having to manually upgrade setuptools within my virtualenvs because the `PyPA has been so prolific with setuptools releases lately <https://pypi.python.org/pypi/setuptools#changes>`_.
One of the subjects I find myself thinking about a lot is: Plone (surprise!) In Plone-land, we deliver the **best Python-based CMS money can't buy on top of an aging Zope 2 "application server"** mixed with newer Zope, Python, and other technologies. In short, this is a challenge.
This was a giant let down, because I was hoping to avoid putting any time in to my blogging infrastructure. For weeks I did nothing. I poked at various options: Pelican, Plone, Tumblr, others. Eventually, I found my way back to Pelican and now I'm happy again.