This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
betahaus.debug
What is betahaus.debug?
A simple utility function for adding a external pdb script that is accessible via url everywhere in the site. This does not add any post-mortem debugger. If you want that use the Products.PDBDebugMode. betahaus.debug only works when in DevelopmentMode.
Installation
- buildout:
add betahaus.debug entries to eggs and zcml in the appropriate buildout configuration file.
re-run buildout.
Install via portal_quickinstaller or Site Setup in plone to get the External method
Usage
Add /pdb to a url and you will get a python debugger on that contenttype where self is the context.
Remember to remove this when putting in production.
Enjoy!
Change history
0.1 (2009-08-29)
Initial release (mlundwall)
Contributors
Martin Lundwall, Author
Release files for betahaus.debug 0.1
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 | |
|---|---|---|---|---|
| betahaus.debug-0.1.tar.gz | 3.6 kB | Without provenance | Details |
Release files / betahaus.debug-0.1.tar.gz
| Download URL | betahaus.debug-0.1.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c22c67c740e0a144a676924eb163d8e901f2c47bbc1dc82d1f72e08dbad0b08
|
|
BLAKE2b-256 checksum How to use checksums |
ff7def2b6be4fa753852aa3bfe9ddc78aca5c034a9745c24521e47d72512ae5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for betahaus.debug 0.1
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.
