I aim to learn the computer language Python while in Beirut for the winter. What Mac OS X Python IDE do you recommend? I am using the new IDE called PyCharm which I like because it works almost exactly like IntelliJ IDEA, my favourite Java IDE. But I want to make sure this is as good as it gets.
What book or resource do you recommend for learning? I’m using the free Python tutorial. Which is okay but I prefer dead trees for this type of thing.
Sounds like a bot right? PokerStars sent a human to verify that it was really a human playing 120 tables at once, or roughly two hands per second A fascinating read.
The latest PokerStars update added some nice new functionality. An unfortunate side-effect is that BlazingStars, the free, open-source poker auto-hotkey program for Mac OS X broke. I’d like to do what I can to fix it but I’d be overcommitting myself. Can you help? You’ll be doing the Mac OS X poker community a favour. You’ll need to know a bit of Objective-C.
I suspect fixing the problem involves simply working out the new co-ordinates of buttons on the screen.
Loyal Poker Copilot customer Randy informed me that PokerStars is now automatically saving tournament summaries. Thank goodness! This makes one of the most common Poker Copilot improvement requests possible.
Here’s what you need to do to activate this:
In PokerStars, from the Menu select “Options” -> “Tournament Summary Options…”.
Check the checkbox labelled “Save My Tournament Summaries”
Change “Keep Tournament Summaries for … Days” to 365
Ensure Language is set to English
Unfortunately Poker Copilot needs a small alteration to be able to read these files. That’s because – at least on my computer – the tournament summaries have a strange hidden character (ASCII #16) at the beginning of the first line.
The next Poker Copilot update will work with these files.
Frequent updates, each containing only a couple of updates? Or infrequent updates with lots of changes? These are the choices I have for Poker Copilot updates.
Frequent Updates
Updating frequently is safer. When an update has a problem, it is easy to track down the problem. I can fully resolve issues from customer feedback before progressing. It keeps the software running well. But it puts a burden on the users of Poker Copilot. They have to update often, which can be somewhat annoying. Sometimes when you start up a piece of software you simply want to use it. Not to go through the update process first.
Frequent updates lead to a new class of support problems: not everybody updates. So I end up with customers running many different updates at once. Before I can analyse any problem I need to ascertain what update the person with the problem is using.
Infrequent Updates
Infrequent updates reduce the burden on the customer. They have to update less frequently. When they do get the chance to update, it is usually worthwhile because there are many improvements. But many changes at once in the software make new problems difficult to diagnose. The changes can magnify problems through combinations of bugs that eluded testing. This is a bad result for everybody: me as the Poker Copilot developer, and customers.
Summary
Neither situation is ideal. I’ve weighed up the advantages and disadvantages. I’m leaning towards continuing with small and frequent updates.
There’s a new experimental feature which allows you to override the detected table size within the HUD. This is mostly of use to AbsolutePoker/UB players, because it is tricky to auto-detect whether a table is 6-max or full size. To turn on this feature, go to the Preferences and check “Allow manual table size override”.
Updated language bundles
The database startup process does an improved optimisation to keep the database running at a rollicking rate.
What’s fixed:
Winamax hands don’t report the timezone correctly. Poker Copilot now auto-detects this problem and fixes them.
I’ve arrived in Beirut, where Poker Copilot will be based for a while. Now that I staying in one city, things have started moving again for the next Poker Copilot update.
It’s great to be once more in a country where the web is uncensored. YouTube, FaceBook, BlogSpot: these, amongst others, were all theoretically inaccessible in neighbouring Syria. Many locals seemed to have no problem getting around these restrictions.
Are you in Beirut or passing through sometime soon? Make sure to let me know so we can have a Poker Copilot meet-up, and perhaps a friendly poker night.
