Lately I’ve been working on integrating (or, more accurately, attempting to integrate) the Python scripting language into some plugins for an application we develop plugins for. We’ve wrapped many libraries with varying levels of success, so this one wasn’t going to be much different. Or, so we thought.

Technically, we’re interested in “Embedding” Python — We have a native Objective-C application that needs to make use of the Python interpreter at various stages of execution. The Python scripts are user-supplied, and are exceptionally free-form: the functions they write can take variable numbers of inputs, produce variable numbers of outputs, and can use any Python modules they have installed.

Unfortunately, this makes the embedding process somewhat complicated: From Objective-C, we need to be able to parse the script, find all its functions, and get all those functions’ input and output parameters. From this data, we can expose the Python module’s interface usefully. Unfortunately, Python does not appear to allow this kind of introspection from the outside (and it’s questionable whether or not it’s even possible from the inside.)

In searching for information on this, Numerous Documents are Found that Needlessly Complicate or Obfuscate the difference between Embedding and Extending. As if it’s really that difficult (embed means “fix firmly and deeply in a surrounding mass” while extend means “cause to cover a larger area; make longer or wider”. From these obvious definitions, we can infer that “Embedding” means putting something inside, while “Extending” means adding functionality or abilities. Maybe it’s not so clear for non-native english speakers. I don’t know.)

Another annoying side-trip of this research was an overwhelmingly smug idea that almost reeks of Java. This side effect is the recorded smarmy discussion of why one should “Extend” rather than “Embed” (these reasons are then used to explain away why there isn’t any good documentation on actually embedding Python). The arguments go something like this:

• Python’s so good, cross-platform, and flexible that it’s actually more cost-effective to Throw Out All Your C/C++/ObjC Code And Rewrite Everything In Python.
• Embedding is so cumbersome to code, and so difficult compared to embedding Python in Python, that you should Throw Out All Your C/C++/ObjC Code And Rewrite Everything In Python.
• High-performance code can be written in C, and then called from within Python’s runtime when you actually need to performance boost. Why not just Throw Out All Your C/C++/ObjC Code And Rewrite Everything In Python Except for the fast bits?
• If you embed Python, you’ll annoy Python developers who can’t access the modules they’re used to using. Why not Throw Out All Your C/C++/ObjC Code And Rewrite Everything In Python so you don’t annoy your Python developers?

These arguments cover some pretty diverse ground there. Unfortunately, there are 2 fatals flaws in the list above.

First, embedded Python _Can_ in fact use installed modules just like raw Python, so point 4 above is flagrantly incorrect. There are some suggestions that it’s simply annoying to develop in such an environment because namespaces are all strange (or wrong) and nothing works quite right. Guess What: Welcome To Plugin Development! It’s like these Python developers have never worked on real projects before or something.

Second, All of the above points assume that it’s possible to discard your entire code-base and rewrite everything. While this is technically possible, it’s not very likely when you don’t have access to the source of the application to be discarded (in our case). The unfortunate downside is that _All The Listed “Solutions” Hinge On This One Idea_.

What’s with these non-solutions from allegedly flexible languages? Even Objective-C, a compiled language, and the (totally undocumented) JavaVM-ObjC bridge, offer enough introspection to at least find methods and parameter counts without too much hassle. Maybe Python does this just as simply, but if so, no one’s talking about it…

I thought to myself this morning — I want an Eggo Waffle. You see, I have never had one, but have always been interested. There were some in the freezer that Robert had bought, removed from their packaging because of his space-saving ways.

Naturally I found the need to prepare an Eggo Waffle to the correct specifications as I wanted to make sure that I was having the correct Eggo experience (microwave, toast, pan fry, what?). To my surprise the feast was ruined (credit for the title), and breakfast was not magically delicious.

Dear Kellogg’s,

I thought to myself this morning — I want an Eggo Waffle. You see, I have never had one, but have always been interested. There were some in the freezer that Robert had bought, removed from their packaging because of his space-saving ways.

However I could NOT find any directions on how to actually make an Eggo Waffle. So I thought to myself — Hey, Eggo’s web site might have this pertinent and useful information! To my surprise I found that the Eggo web site was designed like shit.

No, I cannot enjoy an Eggo waffle for the first time because I simply do not know the proper instructions. This information is surprisingly absent from a web site. Instead I have useless information thrust into my vision in a flash animated piece of shit.

My breakfast appetite is ruined. I am no longer interested in having an Eggo Waffle because your shitty web site design team put me off.

This might be humorous to you or your team, but this is no laughing matter to me. I think I will have some General Mills Cheerios instead.

Love mradcliffe

You might be amused to find my difficulty with preparing an Eggo Waffle. In my search for deliciousness I did come across one link to enjoy Eggo Waffles, which I admit did look interesting. However I wanted to pursue slightly more official instructions. And I did receive an update from Kellogg’s though it came into my inbox a bit too late in the day for breakfast.

Update: Kellogg’s responded! I bet I made someone’s day.

Thank you for contacting us regarding Eggo® website.

The feedback you provided on our website is valuable to us. We will pass along your comments to our advertising and marketing departments. As you know, things change quickly on the web, so we hope you will visit us again to see what’s new!

We hope you give our product another opportunity. For future information you can contact us toll free at 1-800-962-1413 so one of our service representatives could answer your questions.

I am quite surprised that Eggo has a toll free number. So whomever comes across this post — if you need to learn “How-To Make an Eggo Waffle” because you’ve never had one before you can call 1-800-962-1413.

Operators are standing by to assist you with your breakfast endeavor.

The final lesson to be learned is that I am grumpy in the mornings. Never get between a Radcliffe and his breakfast.

Why give us insight?
by Johann Wolfgang von Goethe, translated from the German by me.

Why give us the ability
to see consciously our destiny:
our love, our earthly happiness,
and to blissfully fancy
that we can ignore our foreboding?

Why give us, O Fate, the vision
to look each other in the heart,
to seek out, in the crush of crowds,
our true connection?

Oh, so many thousands of people
in their bland oblivion
barely even know their own hearts.
They wander aimlessly, run
hopelessly in sourceless hurt,
cheering again when quick joy
comes with the unexpected blush of dawn.

Only to us, both unfortunate, full of love,
is that fickle happiness denied:
to love each other without understanding,
each seeing in the other what never really was,
going about in an illusion of happiness
and shrinking only from imaginary dangers.

Happy, who is busied with empty dreams!
Happy, whose premonition is false!
Each presence and each glance for us
only fortifies both dream of happiness
and knowledge of our fate.

Tell me, what does fate think it is doing?
Tell me, how are we so uncannily connected in life?
Oh, you were in some past existence, long ago
already my sister or my wife.

You understood every tremor of my being,
sensed how the purest nerve rang,
could read me with a glance
that was as heavy as dying,

measured drop for drop my hot blood,
righted my wild, haphazard steps,
and in your angelic arms
my ruined heart calmed itself again.

You healed my heart with magical ease,
wound me back together,
and ordered my days.
What bliss filled every blessed hour
that I laid that heart at your feet
and felt it swell next to yours,
felt good in your eyes,
brightened all my senses,
and quieted my rushing blood!

And above all floats a memory
still only in the unconscious heart
that feels the ancient truth forever just barely contained,
and the new circumstance turns it into pain.
And we feel that we are each only half-souled;
twilight is for us the brightest day.
Happy, that the fate that torments us
at least could not take that away.