"own risk"

Ermm.... what?


"The Microsoft (R) File Checksum Integrity Verifier tool is an unsupported command line utility that computes MD5 or SHA1 cryptographic hashes for files. Microsoft does not provide support for this utility. Use this utility at your own risk. Microsoft Technical Support is unable to answer questions about the File Checksum Integrity Verifier. For more information, see Microsoft Knowledge Base Article 841290."

Probably it's just some misunderstanding, but I guess the entire purpose of the procedure is to eliminate some risk ... and of course, if the party distributing stuff is not really taking responsibility in this game, it feels like as if there wasn't any game o.O




source

Today's Easter egg is a Cython default

I bet God is laughing somewhere (everywhere? :) that would just make me feel sooo much better :D ) at me :\

So ...

I er... my code calls a simple function that really indeed takes one single boolean switch (could get "promoted" someday to an Enum) -- until the more descriptive enums come to the picture, I like to be explicit about what argument we're inputting at those early 'let's see if it works' points for clarity; and while the pure Python version was running fine ... of course Cython was quick to jump on my nerves to entertain me :)


"TypeError: ... takes no keyword arguments"

And of course there's an explanation:

"It's an optimisation. If you want to accept keywords for single argument functions, use the always_allow_keywords directive."