Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 # gae_libs | |
| 2 | |
| 3 This [gae\_libs](gae_libs) module is for shared code that depends on App Engine | |
| 4 APIs (gae is short for Google App Engine), eg: an NDB model that supports | |
|
wrengr
2016/11/15 00:38:00
The proper spelling is "e.g.,"
stgao
2016/11/16 18:44:10
Done. Thanks for the correction :)
| |
| 5 keeping multiple versions of the same information like configuration. | |
| 6 | |
| 7 It also depends on the sibling [libs](libs) module, and provides gae wrappers | |
| 8 for the code there, eg: a Gitiles client with data cached in memcache on App | |
| 9 Engine. | |
| 10 | |
| 11 # How to use? | |
| 12 | |
| 13 Create symbolic links to both [gae\_libs](gae_libs) and [libs](libs) in the same | |
| 14 containing directory, and ensure that the containing directory is in sys.path or | |
|
wrengr
2016/11/15 00:38:00
"containing directory" is non-idomatic. Should be
stgao
2016/11/16 18:44:10
It doesn't have to be in the root direction of tha
| |
| 15 PYTHONPATH. | |
| 16 | |
| 17 The usage would look like: `from gae_libs import API_MODULE_NAME` | |
| OLD | NEW |