Overview
Adds functionality to the python debugger, including support for remote debugging
Installation
pip install epdb
Usage
For debugging code locally, epdb generally works the same as pdb. You can debug a program from the python interpreter:
>>> import epdb
>>> import mymodule
>>> epdb.Epdb().run('mymodule.test()')
*** NameError: name 'execfile' is not defined
> /home/wasche/git/epdb/<string>(1)<module>()
-> """
(Epdb) continue
Traceback (most recent call last):
File "<console>", line 1, in <module>
File "/usr/lib64/python3.5/bdb.py", line 431, in run
exec(cmd, globals, locals)
File "<string>", line 1, in <module>
File "/home/wasche/git/epdb/mymodule.py", line 2, in test
import spam
ImportError: No module named 'spam'
You can also drop breakpoints at specific places in a program’s code by inserting:
import epdb; epdb.set_trace()
or by using the alias st:
import epdb; epbd.st()
To debug code that is either running on a remote system, or in a process that isn’t attached to your tty you can use epdb in server mode:
import epdb; epdb.serve()
By default epdb.serve() will start a simple telnet server on port 8080, but you can use the port keyword argument to use a different port:
import epdb; epdb.serve(port=8888)
You can connect to the epdb server by using epdb.connect():
>>> import epdb >>> epdb.connect()
By default epdb.connect() will attempt to connect to port 8080 on localhost. If you are debugging a process on another host or port, you can call connect with the host or port keyword arguments:
>>> import epdb >>> epdb.connect(host='some.host.com', port=8888)
Metadata
Release files for epdb 0.15.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 | Actions |
|---|---|---|---|---|
| epdb-0.15.1.tar.gz | 28.2 kB | Without provenance | Details for epdb-0.15.1.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| epdb-0.15.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for epdb-0.15.1-py2.py3-none-any.whl |
| epdb-0.15.1-py2-none-any.whl | Python 2 | none | any | Details for epdb-0.15.1-py2-none-any.whl |
Total release size: 85.6 kB
Release files / epdb-0.15.1.tar.gz
| Download URL | epdb-0.15.1.tar.gz |
|---|---|
| Size | 28.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f59e9d54866faad6fcbd8fcfc634b85e8fde2b045b13d10f2f8d083f6cbd2668
|
|
BLAKE2b-256 checksum How to use checksums |
60d3e74d7f5f6476b6392f596750b533ff3b3897dd2ef361521661e061ce7766
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / epdb-0.15.1-py2.py3-none-any.whl
| Download URL | epdb-0.15.1-py2.py3-none-any.whl |
|---|---|
| Size | 28.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
4208e310f4ed000b92d40e4fafad3ba67a295e6ecdaae0a3d64380c8c8fac629
|
|
BLAKE2b-256 checksum How to use checksums |
ee6d39b6e602e5bab391f921b752a4e131e10d0dd734a5734b4293ae12e32e36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / epdb-0.15.1-py2-none-any.whl
| Download URL | epdb-0.15.1-py2-none-any.whl |
|---|---|
| Size | 28.7 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
749c7bc9c23e01f1e5238684178b7d61c323647e063ec7f3603678552856e559
|
|
BLAKE2b-256 checksum How to use checksums |
b29427737a2a97422d2bfb70982f06b5b3fdab66b8221a978b752ce938092a50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for epdb 0.15.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.