Skip to content

Instantly share code, notes, and snippets.

View datagrok's full-sized avatar

Michael F. Lamb datagrok

100 followers · 60 following
View GitHub Profile
@datagrok
datagrok / keybase.md
Created April 26, 2017 04:00
keybase proof

Keybase proof

I hereby claim:

  • I am datagrok on github.
  • I am datagrok (https://keybase.io/datagrok) on keybase.
  • I have a public key ASCrSLf3jYbRq3V0I7pJgP1UEqtjxqqP5iTBLfN5VXNq-Qo

To claim this, I am signing this object:

@datagrok
datagrok / LICENSE.AGPL-3.0.md
Last active December 30, 2015 23:49
Various GNU Licenses (GPLv3, AGPLv3, LGPLv3) converted to Markdown format.

GNU AFFERO GENERAL PUBLIC LICENSE

Version 3, 19 November 2007

Copyright © 2007 Free Software Foundation, Inc. http://fsf.org/

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

@datagrok
datagrok / noob-questions.md
Last active September 18, 2015 15:52
Questions while reading stuff

Python

__debug__ vs. -O

Python has a built-in variable __debug__ which is set to True when python is called without -O (optimize). The -O flag disables all assertion code.

This seems at first glance like a very easy and clean construct to rely on when coding in development versus production: in development, don't use -O, defensively litter your code with type- and sanity-checking asserts. Perform development-only debugging by testing __debug__ beforehand.

When in production, run all code is run with -O which disables asserts (speeding execution) and sets __debug__ to False.

@datagrok
datagrok / README.md
Last active August 29, 2015 14:11
Update a directory upon `git push`