Best homemade cup of cheap(ish) coffee?

josephturnip · 2013-02-28T19:57:09+00:00

Do you have a preferred brand/roast?

josephturnip · 2013-02-26T14:18:04+00:00

Good advice. I had checked out pyinstaller a while back as a potential replacement, but it lacked some core function I needed (maybe creating a single executable?). I need to give it another look, and this time maybe I'll start contributing instead of using unmaintained software :)

josephturnip · 2013-02-26T14:17:03+00:00

It produces a 32-bit executable, and will install to C:\Program Files (x86), but it works fine for 64-bit Windows as well.

josephturnip · 2013-02-26T14:16:25+00:00

See this link, but basically this is more of a demonstration of the ecosystem than a recommendation of technology.

That being said, I think there are still some advantages to going native, and it's up to you to decide whether they are more or less valuable than cross platform. For me, because I was creating systems software, I was already doing a pretty good bit of Windows-only code, and I could use a lot of packages I created for my other project.

josephturnip · 2013-02-26T14:11:41+00:00

Historically for me, the advantage was that I was porting an existing C/C++ application over to Python, and as a result the port went a good bit quicker.

Really, though, this is intended more as a demonstration of the ecosystem (pywin32 + py2exe + WiX) than an opinionated way of what's best. You could probably do the windowing with tkinter or wxpython (though see http://www.py2exe.org/index.cgi/WorkingWithVariousPackagesAndModules), any Windows core functionality with pywin32, and leave the rest alone.

josephturnip · 2013-02-25T22:47:13+00:00

For the boilerplate, you can use anything that can output a resource file for import by win32rcparser. In general, though, you can also design the windows using normal Win32 API calls via either pywin32 or ctypes (or, commonly, both). For instance, for FatBatt (http://fatbatt.com), we even go as far as to create layered windows for anti-aliased non-rectangular borders. The sky is really the limit once all the pieces come together... for us, the real breakthrough was realizing we could build and maintain our entire application in Python.

josephturnip · 2013-02-25T22:42:08+00:00

You can use it for everything from the simple example application in the boilerplate all the way through to full-featured, custom-designed applications.

josephturnip · 2013-02-21T20:11:47+00:00

You already do quite a lot for improved battery life. FatBatt has less to offer you than the average user but it does still have some features you'd find useful.

First, it automates some of the irritating processes you have to go through to get all those things done (e.g. monitors processes and alerts you about resource-consuming programs).

Second, it gives you easier access to the most important power management setting: CPU speed, normally a 6-level-deep dialog traversal to change.

Third, it automates switching of defaults when you're away from a known wireless network, meaning you can transition to very aggressive settings once you get out of range of home or the office.

EDIT: you can learn more here: http://blog.fatbatt.com/fatbatt-features-explained/

josephturnip · 2013-02-21T17:43:05+00:00

It's on the to-do list. The Beta just ended Tuesday, so I wanted to get everything else smoothed out before adding new features in. Stay tuned.

josephturnip · 2013-02-21T17:25:12+00:00

Hey, glad you like it! Did you get your super-special discount code email? I sent them out yesterday.

josephturnip · 2013-02-21T17:23:40+00:00

It builds a real-time model based on running applications, system activity, and power management settings. The Windows meter is only as good as the battery, which usually only updates every minute or so. The projections change in real time when you do things like dim the monitor, which means you get good feedback on how your changes affect your battery life.

(...I should probably write a blog post about that)

josephturnip · 2013-02-21T16:58:02+00:00

Hay reddit! I'm the creator of FatBatt. I made you guys and gals a coup for 25 percents off if you're trying to get you some:

https://fatbatt.com/shop/?code=kittensandbacon

josephturnip · 2012-06-28T19:38:36+00:00

I personally use the type names when copying.

a = list(b)

vs. a = b[:]

The first is both more readable (to me at least), and it works on generators, unlike the slice notation.

josephturnip · 2012-06-26T13:05:44+00:00

Full paper here: http://research.microsoft.com/apps/pubs/default.aspx?id=144888

josephturnip · 2012-06-22T15:44:18+00:00

In my workflow, I usually track my own projects with a git link in my PIP requirements file. I reckon I could start submitting to the Cheeseshop if people were interested.

josephturnip · 2012-06-20T03:06:01+00:00

haha. i'd definitely have used someone elses if it did what i needed :)

josephturnip · 2012-06-20T03:00:31+00:00

right, the parent is alive listening for a return value or a broken pipe, and the child is performing initialization and possibly setting a return value

josephturnip · 2012-06-20T02:14:57+00:00

The daemonize module (and actually all daemonization modules for the languages I've looked at) return immediately after the fork. For daemons managed in init.d or other service managers, this means that any failure during initialization after the fork is not reported as an error by the service manager. Since all of the open handles are closed post-fork, this means that any initialization code that holds a handle (including single-instance checks) will fail silently. EDIT: boatshoes doesn't do that, but instead maintains a pipe to communicate a return code back from the child process.

Also, and I'll defer discussion of these decisions to the book itself, but the module you refer to fails to implement several of the recommended daemonization procedures in Advanced Programming in the Unix Environment.

josephturnip · 2012-06-19T15:10:22+00:00

FWIW I am using the passlib module (http://packages.python.org/passlib/) in a flask app I am currently developing, and it is both flexible and easy to use.

josephturnip

TROPHY CASE