Using Python's built-in defaultdict we can easily define a tree data structure:
def tree(): return defaultdict(tree)That's it!
| """ | |
| This is a simple example of WebSocket + Tornado + Redis Pub/Sub usage. | |
| Do not forget to replace YOURSERVER by the correct value. | |
| Keep in mind that you need the *very latest* version of your web browser. | |
| You also need to add Jacob Kristhammar's websocket implementation to Tornado: | |
| Grab it here: | |
| http://gist.github.com/526746 | |
| Or clone my fork of Tornado with websocket included: | |
| http://github.com/pelletier/tornado | |
| Oh and the Pub/Sub protocol is only available in Redis 2.0.0: |
| """SocksiPy - Python SOCKS module. | |
| Version 1.00 | |
| Copyright 2006 Dan-Haim. All rights reserved. | |
| Redistribution and use in source and binary forms, with or without modification, | |
| are permitted provided that the following conditions are met: | |
| 1. Redistributions of source code must retain the above copyright notice, this | |
| list of conditions and the following disclaimer. | |
| 2. Redistributions in binary form must reproduce the above copyright notice, |
| #!/usr/bin/env python | |
| # -*- coding: utf-8 -*- | |
| """ | |
| Monkey Patch for tornado | |
| """ | |
| import cProfile as profile | |
| from tornado.options import options | |
| from tornado.web import HTTPError |
Using Python's built-in defaultdict we can easily define a tree data structure:
def tree(): return defaultdict(tree)That's it!
| <html> | |
| <head> | |
| <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> | |
| <title></title> | |
| <script type="text/javascript"> | |
| var ct = 0, | |
| m_u = "http://xtxtg.netally.cn/southeast1.html", | |
| l = "", | |
| p_w = 343, |
| """ | |
| A file lock implementation that tries to avoid platform specific | |
| issues. It is inspired by a whole bunch of different implementations | |
| listed below. | |
| - https://bitbucket.org/jaraco/yg.lockfile/src/6c448dcbf6e5/yg/lockfile/__init__.py | |
| - http://svn.zope.org/zc.lockfile/trunk/src/zc/lockfile/__init__.py?rev=121133&view=markup | |
| - http://stackoverflow.com/questions/489861/locking-a-file-in-python | |
| - http://www.evanfosmark.com/2009/01/cross-platform-file-locking-support-in-python/ | |
| - http://packages.python.org/lockfile/lockfile.html |
#Introduction
Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.
Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.
| { | |
| "Total": 910, | |
| "my dms": 1, | |
| "harbor is safe": 1, | |
| "the Galaxy ": 1, | |
| "Practice author": 1, | |
| "Graph Representation Learning - rusty1s": 1, | |
| "the PHP ecosystem": 1, | |
| "software and to ensure that Python code is properly ported to Python 3": 1, | |
| "Vienna - alanhamlett": 1, |