Apptrace for Google App Engine
The apptrace package provides a WSGI middleware for tracking memory usage in Google App Engine Python applications.
Since apptrace is meant for development and debugging purposes only, it works with the development appserver of the Google App Engine Python SDK and TyphoonAE. It will definitely not work on the GAE production environment.
Copyright and License
Copyright 2010, 2011 Tobias Rodaebel
This software is released under the Apache License, Version 2.0. You may obtain a copy of the License at
Google App Engine is a trademark of Google Inc.
Requirements
The apptrace package requires Guppy-PE (http://guppy-pe.sourceforge.net) to be installed on your PYTHONPATH. It will be automatically installed when you use the easy_install command.
Installation
The easiest way to install apptrace is (provided that you have setuptools installed) to use easy_install apptrace.
Running Apptrace
In order to run the demo application with apptrace run following commands:
$ apptracectl init demo $ python dev_appserver.py demo
See this wiki page for a more detailed documentation on using apptrace:
Buildout
If you want to tinker with the most recent development version of apptrace, install the development environment by typing following commands:
$ hg clone https://apptrace.googlecode.com/hg apptrace-dev $ cd apptrace-dev $ python bootstrap.py --distribute $ ./bin/buildout
Running Unit Tests
All unit tests can be run by executing the following command:
$ ./bin/python setup.py test --appengine-path=<path to the SDK>
Contact
Tobias Rodaebel <tobias dot rodaebel at googlemail dot com>
CHANGES
Version 0.2.3 (2011-07-21)
Fixes a compatibility issue when importing simplejson.
Version 0.2.2 (2011-01-08)
Fixes an issue where apptrace crashed when tracing old style class objects.
Version 0.2.1 (2010-10-13)
Fixes an issue where some modules haven’t been traced.
Fixes an issue where the code browser wasn’t able to load modules from the SDK.
Version 0.2.0 (2010-10-12)
Adds simple code browser.
Version 0.1.1 (2010-10-02)
Uses a separate memcache namespace for storing records.
Version 0.1.0 (2010-10-01)
Initial revision.
Metadata
Release files for apptrace 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| apptrace-0.2.3.tar.gz | 245.3 kB | Without provenance | Details for apptrace-0.2.3.tar.gz |
Release files / apptrace-0.2.3.tar.gz
| Download URL | apptrace-0.2.3.tar.gz |
|---|---|
| Size | 245.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c0b3df5989f5e8c7f677ff2febf2ecd8dbd68c864be0dbdef2fd333d0c94930
|
|
BLAKE2b-256 checksum How to use checksums |
0452cf57fa9598167dc23e8f1ce9606c029c26dd560d0d65b1fa1d80a3e94c25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for apptrace 0.2.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.