This is an example of how to generate occurrences from python-dateutil's rrule module, and convert them properly to UTC before saving to the database, particularly if your input is localized to a timezone that observes daylight savings. This assumes your server time is localized, otherwise if it's UTC you probably won't run into these problems.
Note: US daylight savings in 2014 started on March 9
The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Wed, 14 Nov 2012 03:35:10 GMT till Thu, 14 Nov 2013 03:35:10 GMT.
Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search. Sorting algo in pseudocode:
githubUsers
.filter((user) -> user.followers > 0)| # -*- coding: utf-8 -*- | |
| """ | |
| sphinx.builders.mobi | |
| ~~~~~~~~~~~~~~~~~~~~ | |
| Build mobi files. | |
| Originally derived from epub.py. | |
| :copyright: Copyright 2007-2011 by the Sphinx team, see AUTHORS. | |
| :license: BSD, see LICENSE for details. |
Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000
git clone git://github.com/kohana/kohana yourdomain.com
cd yourdomain.com
git submodule update --init
rm install.php
cd application
chmod 0777 cache
chmod 0777 logs
| /* ========================================================================= | |
| CurveZMQ - authentication and confidentiality for 0MQ | |
| ------------------------------------------------------------------------- | |
| Copyright (c) 1991-2013 iMatix Corporation <www.imatix.com> | |
| Copyright other contributors as noted in the AUTHORS file. | |
| This is free software; you can redistribute it and/or modify it under | |
| the terms of the GNU Lesser General Public License as published by | |
| the Free Software Foundation; either version 3 of the License, or (at |
A slightly updated version of this doc is here on my website.
I visited with PagerDuty yesterday for a little Friday beer and pizza. While there I got started talking about Go. I was asked by Alex, their CEO, why I liked it. Several other people have asked me the same question recently, so I figured it was worth posting.
The first 1/2 of Go's concurrency story. Lightweight, concurrent function execution. You can spawn tons of these if needed and the Go runtime multiplexes them onto the configured number of CPUs/Threads as needed. They start with a super small stack that can grow (and shrink) via dynamic allocation (and freeing). They are as simple as go f(x), where f() is a function.
| #Modified and simplified version of https://www.windowsazure.com/en-us/develop/net/common-tasks/continuous-delivery/ | |
| $subscription = "[Your Subscription Name]" | |
| $service = "[Your Azure Service Name]" | |
| $slot = "staging" #staging or production | |
| $package = "[ProjectName]\bin\[BuildConfigName]\app.publish\[ProjectName].cspkg" | |
| $configuration = "[ProjectName]\bin\[BuildConfigName]\app.publish\ServiceConfiguration.Cloud.cscfg" | |
| $timeStampFormat = "g" | |
| $deploymentLabel = "ContinuousDeploy to $service v%build.number%" | |
| Write-Output "Running Azure Imports" |
| #!/usr/bin/python | |
| # This code is public domain, share and enjoy. | |
| import random, re, sys, os | |
| seed = None | |
| if len(sys.argv) > 1: | |
| seed = int(sys.argv[1]) |