| ּ_בּ | |
| בּ_בּ | |
| טּ_טּ | |
| כּ‗כּ | |
| לּ_לּ | |
| מּ_מּ | |
| סּ_סּ | |
| תּ_תּ | |
| ٩(×̯×)۶ | |
| ٩(̾●̮̮̃̾•̃̾)۶ |
| A JSON file of GitHub's emojicodes and emoji. Unlike other projects, | |
| this one includes the actual emoji and does not alter GitHub's list. | |
| Also included is a JSON file formatted for use with the Auto Text | |
| Expander extension for Google Chrome, with text to be expanded based | |
| on GitHub's ":EMOJICODE:". | |
| See README.md for details. | |
| # coding: utf-8 | |
| # Barcode scanner demo for Pythonista | |
| # Based on http://www.infragistics.com/community/blogs/torrey-betts/archive/2013/10/10/scanning-barcodes-with-ios-7-objective-c.aspx | |
| from objc_util import * | |
| from ctypes import c_void_p | |
| import ui | |
| import sound | |
| found_codes = set() |
It's not unusual for web application developers to write UIs that impose some restrictions on the user, but don't employ those same restrictions in the APIs to which those UIs send data. The APIs are written with the assumption the UI has prevented the user from sending invalid input. What happens when those APIs are used with a different UI or no UI at all?
A UI lets the user enter an email address. The UI disallows the user from entering some valid email
| import photos |
| import os, os.path, sys, urllib2, requests, tempfile, zipfile, shutil, gzip, tarfile | |
| __pypi_base__ = os.path.abspath(os.path.dirname(__file__)) | |
| class PyPiError(Exception): | |
| def __init__(self, value): | |
| self.value = value | |
| def __str__(self): | |
| return repr(self.value) |
| # Standalone mini version of pip | |
| # Geared towards Pythonista, but easily adaptable to other pure python installs | |
| import argparse, copy, gzip, os, os.path, re, requests, shutil, site, sys, tarfile, time, xmlrpclib | |
| # Where packages will end up installed | |
| site_packages = site.USER_SITE | |
| # Root of Pythonista saveable document location | |
| pythonista_base = os.path.split(site_packages)[0] | |
| # Temporary directory for work |
There are times notifications aren't wanted about either a changed repo file or a new file that needs to be added to the repo. However, adding the name of the file to .gitignore might not be a good option, either. For example, locally-generated files that other users aren't likely to generate (e.g., files created by an editor) or files of experimental test code might not be appropriate to appear in a .gitignore file.
In those cases, use one of these solutions:
If the file is a changed repo file
Use the command:
git update-index --assume-unchanged "$FILE"
| #!/bin/bash -- | |
| # File containing the process ID of the application, written by the application | |
| PID_FILE='app.pid' | |
| # The process name or some string unique to the application's process | |
| PROCESS_NAME="java -Dspring.config.location=${HOME}/application.properties" | |
| [[ $# -gt 0 && $1 = '-v' ]] && VERBOSE=1 |
| #!/bin/sh -- | |
| # Save as "git-exclude" and set the executable flag. | |
| # Execute as "git exclude repo_path file_path" | |
| if [ $# -ne 2 ]; then | |
| echo "usage: $(basename $0 | sed 's/-/ /g') <repo-dir> <file-path>" > /dev/stderr | |
| exit $(false) | |
| fi |