Readying first alpha release, but where to install MySQL Connector/Python?

I’m currently planning a first ‘alpha’ release of MySQL Connector/Python, but I’m now doubting whether the naming and installation of the module is actually good. Currently, the module lives, in site-packages/mysql/connector/, or import mysql.connector. Since this is an official MySQL, sorry, Sun Microsystems, project, I thought that the ‘parent’ module mysql would be good enough. But is it? Would it break your modules with the same name? The idea was to make more tools for Python and have them all under the mysql module, but maybe we need a smarter name for this?

Most popular websites are just broken: no language option!

So, I’m in Poland right now. I check my Google account: it’s in Polish. No way to set it in English, though my browser preferences are set so. You would have thought smart people work at Google, right? No, the broken way to set language: based on IP address. What’s even more idiotic is the fact that you can’t actually change to English (or your favorite language). (see screenshot)

Reducing paper mail

This is not about email, but the mail dropped into the mailbox at home.. Take the none important letters and stupid magazines and tell the folks you don’t want to get anything at home anymore. At least in Germany, it worked well today telling them through email, phone call and going in person. Tomorrow I should do a few more to make sure no junk mail is littered in my box.

Make MySQL refuse connections until data nodes are started

MySQL Cluster 6.3.28 and 7.0.9 introduce the MySQL server option --ndb-wait-setup. This makes sure that clients can not connect the SQL Node when no Data Nodes are available within, by default, 15 seconds. When the timeout is reached, and no Data Nodes are available, the NDB storage engine will be marked as unavailable. The following will appear in the MySQL server error log when --ndb-wait-setup=30 has been set: [Note] NDB: NodeID is 10, management server 'ndbsup-priv-1:1406' [Note] NDB[0]: NodeID: 10, **no storage nodes connected (timed out)** [Note] Starting Cluster Binlog Thread [Note] Event Scheduler: Loaded 0 events [Note] NDB Binlog: Ndb tables initially read only.

Resize and set default column size in Mac OS X Finder

This bugged me for a long time, and just today I googled for a solution. And it’s darn simple! To set a new default column size, size them while holding the Option (Alt) key. Open a new Finder window, et voila: default size changed! There are lots of these little tricks in Mac OS (and I’m sure in other desktop GUIs). Fun to find one each day!