This package provides a profiler skin which allows you to profile pages.
Detailed Documentation
Web-based Profiler
This package offers a profiler including a skin. This profiler allows you to profile views on a existing Zope3 application.
Let’s access the profiler start page:
>>> from z3c.etestbrowser.testing import ExtendedTestBrowser
>>> user = ExtendedTestBrowser()
>>> user.addHeader('Accept-Language', 'en')
>>> user.open('http://localhost/++skin++Profiler')
If you access the profiler, you can push the start button:
>>> user.getControl('Start').click()
>>> 'Show Profile' in user.contents
True
Now we can go to the help.html page which gets profiled. Let’s use another browser for this.
>>> newBrowser = ExtendedTestBrowser()
>>> newBrowser.open('http://localhost/++skin++Profiler/help.html')
>>> newBrowser.url
'http://localhost/++skin++Profiler/help.html'
After calling the help.html page, we can go to the doProfile page and show the profile by clicking on the Show Profile button:
>>> user.getControl('Show Profile').click()
If we whould not call this form within this test, we whould see the profile data table. But we do not see the profile data table. Probably the testrunner conflicts with the monkey call.
>>> print user.contents
<!DOCTYPE ...
<div>
No data available.
</div>
...
Changes
0.10.0 (2010-08-19)
Using python’s doctest module instead of deprecated zope.testing.doctest.
Fixed bin/app by requiring zope.login.
Removed some not needed dependecies: zope.app.generations, zope.app.pagetemplate, z3c.coverage.
Moved dependency on zope.app.server to an app extra in setup.py as the tests do not need it and the profiler may be used in a WSGI application then it is not needed, too.
Declared zope.dublincore in app extra, too, as it is not needed by the tests but bin/app requires now version 3.7 to run.
0.9.0 (2009-12-26)
Use zope.browserpage and zope.browserresource instead of zope.app.publisher.
0.8.1 (2009-12-26)
Fixed processing profile data for display in web UI, so the data is now displayed on the web page. Kept the previous behavior to print unprocessed profile data on stdout.
Removed unused dependency on z3c.i18n.
Removed not necessary and undeclared test depenency on zope.app.authentication.
Removed zpkg and ZCML install slugs.
0.8.0 (2009-06-19)
Removed no longer necessary dependencies on zope.app.zapi, zope.app.container, zope.app.component, zope.app.security.
Removed dependency on z3c.layer.minimal, as it is not used.
Removed no longer necessary test dependencies on zope.app.folder, zope.app.session, zope.app.schema.
0.7.1 (2009-04-05)
Removed unnecessary dependencies on zope.app.twisted and zope.app.zopeappgenerations.
0.7.0 (2009-03-14)
Use current zope.configuration instead of deprecated zc.configuration to get exclude directive.
0.6.0 (2009-02-19)
No longer uses deprecated z3c.layer.
Fixed dependencies and tests.
0.5.1 (2008-01-24)
Bug: Fixed meta-data.
Bug: Fixed deprecation warning about the Zope Security Policy.
0.5.0 (2008-01-21)
Initial Release
Metadata
Release files for z3c.profiler 0.10.0
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 |
|---|---|---|---|---|
| z3c.profiler-0.10.0.tar.gz | 104.4 kB | Without provenance | Details for z3c.profiler-0.10.0.tar.gz |
Release files / z3c.profiler-0.10.0.tar.gz
| Download URL | z3c.profiler-0.10.0.tar.gz |
|---|---|
| Size | 104.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3771d0a35fd3902873568fd7a293cff9852ecc542e0b8187a360210316c759fe
|
|
BLAKE2b-256 checksum How to use checksums |
520f9b824bad131c60aaf9bd34961f7a8e9a54f9f879855e467bb14ec2e85051
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for z3c.profiler 0.10.0
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.
