| This is free and unencumbered software released into the public domain. | |
| Anyone is free to copy, modify, publish, use, compile, sell, or | |
| distribute this software, either in source code form or as a compiled | |
| binary, for any purpose, commercial or non-commercial, and by any | |
| means. | |
| In jurisdictions that recognize copyright laws, the author or authors | |
| of this software dedicate any and all copyright interest in the | |
| software to the public domain. We make this dedication for the benefit |
| import sys,os | |
| import curses | |
| def draw_menu(stdscr): | |
| k = 0 | |
| cursor_x = 0 | |
| cursor_y = 0 | |
| # Clear and refresh the screen for a blank canvas | |
| stdscr.clear() |
This is a continuation of my buffer pre-write hook series. Check out the previous gist to follow the progression.
Have you ever tried running a file only to be stopped by "<<<<<<<"?
Wouldn't it be nice to be able to automatically run your code through pyflakes before actually saving it? Maybe even raise an error for showstopping bugs in your code?
development https://git.heroku.com/xxx.git (fetch)
development https://git.heroku.com/xxx.git (push)
origin [email protected]:xxx/xxx.git (fetch)
origin [email protected]:xxx/xxx.git (push)
production https://git.heroku.com/xxx.git (fetch)
production https://git.heroku.com/xxx.git (push)
staging https://git.heroku.com/xxx.git (fetch)
Short (72 chars or less) summary
More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).
Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages
| """Written on iPhone with the Pythonista 3 app | |
| As a joke for the PyBites guys, I don't see why it wouldn't work anywhere else though. They always | |
| start off their newsletter annoucements with: | |
| from @PyBites import newsletter | |
| So I turned it into actual code that pulls their feed and opens their latest newsletter in a browser :) | |
| """ | |
| import os |
| PYBITES_IMG = """ | |
| ;;;;;;;;,,.` | |
| :;;;;;;;;;;::,,,,, | |
| `.............`.`....````.``........`..`..``````````````````````````````````````````````````````````````````````````````````````;, ,;;;;;;;;:,,,,,,,,`````````````````` | |
| `.....................``..................```````````````````````````````````````````` ``,,``````````````````````````````````:;. .;;;;;;;;::,,,,,:::,```````````````` | |
| `.....................`.`.............` `,`````````````````````````````. +`,`````````` `,.`````````````````````````````````:,;;;;;;;;;;;;::::::::::::``````````````` | |
| `...............................``.,,.``.`````````````````````````````####+'.````````` `..```````````````````````````````,,,:;;;;;;;;;;;;:,:::::::::::````````````` |
I am a big fan of the syntastic package. In python, it is useful for viewing both Pyflakes and Bandit errors. However, this only works if syntastic knows what python interpreter to use. Not everyone is fortunate enough to have upgraded all of their software to python3. For reasons out of my control, I end up spending most of my time writing python2 code. This means that the times when I finally get to write python3, all of my syntax checking is broken. How cool would it be to have VIM determine what version of python to use automatically? So, begins my grand experiment...
For this to work, I will be using a virtualenv for python2 and one for python3. It's not absolutely necessary to use virtualenvs but I definitely recommend it. Setting up virtualenvs is out of the scope of this gist but make sure that each virtualenv
| """ | |
| Script to post a code snippet to PyBites CodeImag.es | |
| If you see other use cases (e.g. process a csv file with snippets), | |
| contact @bbelderbos on Twitter, thanks. | |
| """ | |
| from pprint import pprint as pp | |
| # pip install requests python-decouple | |
| import requests | |
| from decouple import config |