A commenter on an earlier entry noted that patchadd 's exit codes are apparently not documented because they'reconsidered an internal implementation detail that might change at somepoint. Unfortunately this is bogus logic.

There's a simple rule: once you explicitly expose something to users, itceases to be an internal implementation detail in practice no matterwhat you want (and no matter what you may claim in documentation,although Sun does not explicitly claim this in the patchadd manpage).

Solaris 9 manifestly exposes patchadd 's

Sam Ruby has a problem: he has too many feeds .Specifically, he has a comment feed for every blog entry, and toomany robots and abandoned aggregators are pulling them, over and overagain, despite the feeds effectively being dead. (See his entry for his solution.)

Sam Ruby isn't alone in having this problem ; anyone with a lot of flexiblesyndication feeds is going to encounter it sooner or later . (Even if you have only a few humanreaders, some search robots love syndication

A posting today to the LiveJournal python_dev community wound up sort of askingwhy del has to be a Python builtin instead of a method. At first Ithought this had a nice simple answer, but the more I thought about itthe less obvious it became, and by the time I'd worked out a satisfyinganswer I'd had to really think about how Python fits together.

The short summary is that del needs to be a builtin because Python'sobject model is based on references and namespaces