Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

Repo symbol

tblib repository

tblib

Repository Summary

Checkout URI https://github.com/ionelmc/python-tblib.git
VCS Type git
VCS Version master
Last Updated 2025-03-31
Dev Status MAINTAINED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

Name Version
tblib 1.2.0

README

Overview


docs Documentation Status tests GitHub Actions Build Status Coverage Status package PyPI Package latest release PyPI Wheel Supported versions Supported implementations Commits since latest release ——— ———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————–

Serialization library for Exceptions and Tracebacks.

  • Free software: BSD license

It allows you to:

  • Pickle tracebacks and raise exceptions with pickled tracebacks in different processes. This allows better error handling when running code over multiple processes (imagine multiprocessing, billiard, futures, celery etc).
  • Create traceback objects from strings (the from_string method). No pickling is used.
  • Serialize tracebacks to/from plain dicts (the from_dict and to_dict methods). No pickling is used.
  • Raise the tracebacks created from the aforementioned sources.
  • Pickle an Exception together with its traceback and exception chain (raise ... from ...) (Python 3 only)

Again, note that using the pickle support is completely optional. You are solely responsible for security problems should you decide to use the pickle support.

Installation

pip install tblib

Documentation

::: {.contents local=””} :::

Pickling tracebacks

Note: The traceback objects that come out are stripped of some attributes (like variables). But you'll be able to raise exceptions with those tracebacks or print them - that should cover 99% of the usecases.

>>> from tblib import pickling_support
>>> pickling_support.install()
>>> import pickle, sys
>>> def inner_0():
...     raise Exception('fail')
...
>>> def inner_1():
...     inner_0()
...
>>> def inner_2():
...     inner_1()
...
>>> try:
...     inner_2()
... except:
...     s1 = pickle.dumps(sys.exc_info())
...
>>> len(s1) > 1
True
>>> try:
...     inner_2()
... except:
...     s2 = pickle.dumps(sys.exc_info(), protocol=pickle.HIGHEST_PROTOCOL)
...
>>> len(s2) > 1
True

>>> try:
...     import cPickle
... except ImportError:
...     import pickle as cPickle
>>> try:
...     inner_2()
... except:
...     s3 = cPickle.dumps(sys.exc_info(), protocol=pickle.HIGHEST_PROTOCOL)
...
>>> len(s3) > 1
True

Unpickling tracebacks

>>> pickle.loads(s1)
(<...Exception'>, Exception('fail'...), <traceback object at ...>)

>>> pickle.loads(s2)
(<...Exception'>, Exception('fail'...), <traceback object at ...>)

>>> pickle.loads(s3)
(<...Exception'>, Exception('fail'...), <traceback object at ...>)

Raising

>>> from six import reraise
>>> reraise(*pickle.loads(s1))

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

Bug reports

When reporting a bug please include:

  • Your operating system name and version.
  • Any details about your local setup that might be helpful in troubleshooting.
  • Detailed steps to reproduce the bug.

Documentation improvements

tblib could always use more documentation, whether as part of the official tblib docs, in docstrings, or even on the web in blog posts, articles, and such.

Feature requests and feedback

The best way to send feedback is to file an issue at https://github.com/ionelmc/python-tblib/issues.

If you are proposing a feature:

  • Explain in detail how it would work.
  • Keep the scope as narrow as possible, to make it easier to implement.
  • Remember that this is a volunteer-driven project, and that code contributions are welcome :)

Development

To set up [python-tblib]{.title-ref} for local development:

  1. Fork python-tblib (look for the "Fork" button).

  2. Clone your fork locally:

    git clone git@github.com:YOURGITHUBNAME/python-tblib.git
    
  3. Create a branch for local development:

    git checkout -b name-of-your-bugfix-or-feature
    

    Now you can make your changes locally.

  4. When you're done making changes run all the checks and docs builder with one command:

    tox
    
  5. Commit your changes and push your branch to GitHub:

    git add .
    git commit -m "Your detailed description of your changes."
    git push origin name-of-your-bugfix-or-feature
    
  6. Submit a pull request through the GitHub website.

Pull Request Guidelines

If you need some code review or feedback while you're developing the code just make the pull request.

For merging, you should:

  1. Include passing tests (run tox).
  2. Update documentation when there's new API, functionality etc.
  3. Add a note to CHANGELOG.rst about the changes.
  4. Add yourself to AUTHORS.rst.

Tips

To run a subset of tests:

tox -e envname -- pytest -k test_myfeature

To run all the test environments in parallel:

tox -p auto
# Contributing Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given. ## Bug reports When [reporting a bug](https://github.com/ionelmc/python-tblib/issues) please include: > - Your operating system name and version. > - Any details about your local setup that might be helpful in > troubleshooting. > - Detailed steps to reproduce the bug. ## Documentation improvements tblib could always use more documentation, whether as part of the official tblib docs, in docstrings, or even on the web in blog posts, articles, and such. ## Feature requests and feedback The best way to send feedback is to file an issue at . If you are proposing a feature: - Explain in detail how it would work. - Keep the scope as narrow as possible, to make it easier to implement. - Remember that this is a volunteer-driven project, and that code contributions are welcome :) ## Development To set up [python-tblib]{.title-ref} for local development: 1. Fork [python-tblib](https://github.com/ionelmc/python-tblib) (look for the \"Fork\" button). 2. Clone your fork locally: git clone git@github.com:YOURGITHUBNAME/python-tblib.git 3. Create a branch for local development: git checkout -b name-of-your-bugfix-or-feature Now you can make your changes locally. 4. When you\'re done making changes run all the checks and docs builder with one command: tox 5. Commit your changes and push your branch to GitHub: git add . git commit -m "Your detailed description of your changes." git push origin name-of-your-bugfix-or-feature 6. Submit a pull request through the GitHub website. ### Pull Request Guidelines If you need some code review or feedback while you\'re developing the code just make the pull request. For merging, you should: 1. Include passing tests (run `tox`). 2. Update documentation when there\'s new API, functionality etc. 3. Add a note to `CHANGELOG.rst` about the changes. 4. Add yourself to `AUTHORS.rst`. ### Tips To run a subset of tests: tox -e envname -- pytest -k test_myfeature To run all the test environments in *parallel*: tox -p auto
Repo symbol

tblib repository

tblib

Repository Summary

Checkout URI https://github.com/ionelmc/python-tblib.git
VCS Type git
VCS Version master
Last Updated 2025-03-31
Dev Status MAINTAINED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

Name Version
tblib 1.2.0

README

Overview


docs Documentation Status tests GitHub Actions Build Status Coverage Status package PyPI Package latest release PyPI Wheel Supported versions Supported implementations Commits since latest release ——— ———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————–

Serialization library for Exceptions and Tracebacks.

  • Free software: BSD license

It allows you to:

  • Pickle tracebacks and raise exceptions with pickled tracebacks in different processes. This allows better error handling when running code over multiple processes (imagine multiprocessing, billiard, futures, celery etc).
  • Create traceback objects from strings (the from_string method). No pickling is used.
  • Serialize tracebacks to/from plain dicts (the from_dict and to_dict methods). No pickling is used.
  • Raise the tracebacks created from the aforementioned sources.
  • Pickle an Exception together with its traceback and exception chain (raise ... from ...) (Python 3 only)

Again, note that using the pickle support is completely optional. You are solely responsible for security problems should you decide to use the pickle support.

Installation

pip install tblib

Documentation

::: {.contents local=””} :::

Pickling tracebacks

Note: The traceback objects that come out are stripped of some attributes (like variables). But you'll be able to raise exceptions with those tracebacks or print them - that should cover 99% of the usecases.

>>> from tblib import pickling_support
>>> pickling_support.install()
>>> import pickle, sys
>>> def inner_0():
...     raise Exception('fail')
...
>>> def inner_1():
...     inner_0()
...
>>> def inner_2():
...     inner_1()
...
>>> try:
...     inner_2()
... except:
...     s1 = pickle.dumps(sys.exc_info())
...
>>> len(s1) > 1
True
>>> try:
...     inner_2()
... except:
...     s2 = pickle.dumps(sys.exc_info(), protocol=pickle.HIGHEST_PROTOCOL)
...
>>> len(s2) > 1
True

>>> try:
...     import cPickle
... except ImportError:
...     import pickle as cPickle
>>> try:
...     inner_2()
... except:
...     s3 = cPickle.dumps(sys.exc_info(), protocol=pickle.HIGHEST_PROTOCOL)
...
>>> len(s3) > 1
True

Unpickling tracebacks

>>> pickle.loads(s1)
(<...Exception'>, Exception('fail'...), <traceback object at ...>)

>>> pickle.loads(s2)
(<...Exception'>, Exception('fail'...), <traceback object at ...>)

>>> pickle.loads(s3)
(<...Exception'>, Exception('fail'...), <traceback object at ...>)

Raising

>>> from six import reraise
>>> reraise(*pickle.loads(s1))

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

Bug reports

When reporting a bug please include:

  • Your operating system name and version.
  • Any details about your local setup that might be helpful in troubleshooting.
  • Detailed steps to reproduce the bug.

Documentation improvements

tblib could always use more documentation, whether as part of the official tblib docs, in docstrings, or even on the web in blog posts, articles, and such.

Feature requests and feedback

The best way to send feedback is to file an issue at https://github.com/ionelmc/python-tblib/issues.

If you are proposing a feature:

  • Explain in detail how it would work.
  • Keep the scope as narrow as possible, to make it easier to implement.
  • Remember that this is a volunteer-driven project, and that code contributions are welcome :)

Development

To set up [python-tblib]{.title-ref} for local development:

  1. Fork python-tblib (look for the "Fork" button).

  2. Clone your fork locally:

    git clone git@github.com:YOURGITHUBNAME/python-tblib.git
    
  3. Create a branch for local development:

    git checkout -b name-of-your-bugfix-or-feature
    

    Now you can make your changes locally.

  4. When you're done making changes run all the checks and docs builder with one command:

    tox
    
  5. Commit your changes and push your branch to GitHub:

    git add .
    git commit -m "Your detailed description of your changes."
    git push origin name-of-your-bugfix-or-feature
    
  6. Submit a pull request through the GitHub website.

Pull Request Guidelines

If you need some code review or feedback while you're developing the code just make the pull request.

For merging, you should:

  1. Include passing tests (run tox).
  2. Update documentation when there's new API, functionality etc.
  3. Add a note to CHANGELOG.rst about the changes.
  4. Add yourself to AUTHORS.rst.

Tips

To run a subset of tests:

tox -e envname -- pytest -k test_myfeature

To run all the test environments in parallel:

tox -p auto
# Contributing Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given. ## Bug reports When [reporting a bug](https://github.com/ionelmc/python-tblib/issues) please include: > - Your operating system name and version. > - Any details about your local setup that might be helpful in > troubleshooting. > - Detailed steps to reproduce the bug. ## Documentation improvements tblib could always use more documentation, whether as part of the official tblib docs, in docstrings, or even on the web in blog posts, articles, and such. ## Feature requests and feedback The best way to send feedback is to file an issue at . If you are proposing a feature: - Explain in detail how it would work. - Keep the scope as narrow as possible, to make it easier to implement. - Remember that this is a volunteer-driven project, and that code contributions are welcome :) ## Development To set up [python-tblib]{.title-ref} for local development: 1. Fork [python-tblib](https://github.com/ionelmc/python-tblib) (look for the \"Fork\" button). 2. Clone your fork locally: git clone git@github.com:YOURGITHUBNAME/python-tblib.git 3. Create a branch for local development: git checkout -b name-of-your-bugfix-or-feature Now you can make your changes locally. 4. When you\'re done making changes run all the checks and docs builder with one command: tox 5. Commit your changes and push your branch to GitHub: git add . git commit -m "Your detailed description of your changes." git push origin name-of-your-bugfix-or-feature 6. Submit a pull request through the GitHub website. ### Pull Request Guidelines If you need some code review or feedback while you\'re developing the code just make the pull request. For merging, you should: 1. Include passing tests (run `tox`). 2. Update documentation when there\'s new API, functionality etc. 3. Add a note to `CHANGELOG.rst` about the changes. 4. Add yourself to `AUTHORS.rst`. ### Tips To run a subset of tests: tox -e envname -- pytest -k test_myfeature To run all the test environments in *parallel*: tox -p auto
Repo symbol

tblib repository

Repo symbol

tblib repository

tblib

Repository Summary

Checkout URI https://github.com/ionelmc/python-tblib.git
VCS Type git
VCS Version master
Last Updated 2025-03-31
Dev Status MAINTAINED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

Name Version
tblib 1.2.0

README

Overview


docs Documentation Status tests GitHub Actions Build Status Coverage Status package PyPI Package latest release PyPI Wheel Supported versions Supported implementations Commits since latest release ——— ———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————–

Serialization library for Exceptions and Tracebacks.

  • Free software: BSD license

It allows you to:

  • Pickle tracebacks and raise exceptions with pickled tracebacks in different processes. This allows better error handling when running code over multiple processes (imagine multiprocessing, billiard, futures, celery etc).
  • Create traceback objects from strings (the from_string method). No pickling is used.
  • Serialize tracebacks to/from plain dicts (the from_dict and to_dict methods). No pickling is used.
  • Raise the tracebacks created from the aforementioned sources.
  • Pickle an Exception together with its traceback and exception chain (raise ... from ...) (Python 3 only)

Again, note that using the pickle support is completely optional. You are solely responsible for security problems should you decide to use the pickle support.

Installation

pip install tblib

Documentation

::: {.contents local=””} :::

Pickling tracebacks

Note: The traceback objects that come out are stripped of some attributes (like variables). But you'll be able to raise exceptions with those tracebacks or print them - that should cover 99% of the usecases.

>>> from tblib import pickling_support
>>> pickling_support.install()
>>> import pickle, sys
>>> def inner_0():
...     raise Exception('fail')
...
>>> def inner_1():
...     inner_0()
...
>>> def inner_2():
...     inner_1()
...
>>> try:
...     inner_2()
... except:
...     s1 = pickle.dumps(sys.exc_info())
...
>>> len(s1) > 1
True
>>> try:
...     inner_2()
... except:
...     s2 = pickle.dumps(sys.exc_info(), protocol=pickle.HIGHEST_PROTOCOL)
...
>>> len(s2) > 1
True

>>> try:
...     import cPickle
... except ImportError:
...     import pickle as cPickle
>>> try:
...     inner_2()
... except:
...     s3 = cPickle.dumps(sys.exc_info(), protocol=pickle.HIGHEST_PROTOCOL)
...
>>> len(s3) > 1
True

Unpickling tracebacks

>>> pickle.loads(s1)
(<...Exception'>, Exception('fail'...), <traceback object at ...>)

>>> pickle.loads(s2)
(<...Exception'>, Exception('fail'...), <traceback object at ...>)

>>> pickle.loads(s3)
(<...Exception'>, Exception('fail'...), <traceback object at ...>)

Raising

>>> from six import reraise
>>> reraise(*pickle.loads(s1))

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.

Bug reports

When reporting a bug please include:

  • Your operating system name and version.
  • Any details about your local setup that might be helpful in troubleshooting.
  • Detailed steps to reproduce the bug.

Documentation improvements

tblib could always use more documentation, whether as part of the official tblib docs, in docstrings, or even on the web in blog posts, articles, and such.

Feature requests and feedback

The best way to send feedback is to file an issue at https://github.com/ionelmc/python-tblib/issues.

If you are proposing a feature:

  • Explain in detail how it would work.
  • Keep the scope as narrow as possible, to make it easier to implement.
  • Remember that this is a volunteer-driven project, and that code contributions are welcome :)

Development

To set up [python-tblib]{.title-ref} for local development:

  1. Fork python-tblib (look for the "Fork" button).

  2. Clone your fork locally:

    git clone git@github.com:YOURGITHUBNAME/python-tblib.git
    
  3. Create a branch for local development:

    git checkout -b name-of-your-bugfix-or-feature
    

    Now you can make your changes locally.

  4. When you're done making changes run all the checks and docs builder with one command:

    tox
    
  5. Commit your changes and push your branch to GitHub:

    git add .
    git commit -m "Your detailed description of your changes."
    git push origin name-of-your-bugfix-or-feature
    
  6. Submit a pull request through the GitHub website.

Pull Request Guidelines

If you need some code review or feedback while you're developing the code just make the pull request.

For merging, you should:

  1. Include passing tests (run tox).
  2. Update documentation when there's new API, functionality etc.
  3. Add a note to CHANGELOG.rst about the changes.
  4. Add yourself to AUTHORS.rst.

Tips

To run a subset of tests:

tox -e envname -- pytest -k test_myfeature

To run all the test environments in parallel:

tox -p auto
# Contributing Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given. ## Bug reports When [reporting a bug](https://github.com/ionelmc/python-tblib/issues) please include: > - Your operating system name and version. > - Any details about your local setup that might be helpful in > troubleshooting. > - Detailed steps to reproduce the bug. ## Documentation improvements tblib could always use more documentation, whether as part of the official tblib docs, in docstrings, or even on the web in blog posts, articles, and such. ## Feature requests and feedback The best way to send feedback is to file an issue at . If you are proposing a feature: - Explain in detail how it would work. - Keep the scope as narrow as possible, to make it easier to implement. - Remember that this is a volunteer-driven project, and that code contributions are welcome :) ## Development To set up [python-tblib]{.title-ref} for local development: 1. Fork [python-tblib](https://github.com/ionelmc/python-tblib) (look for the \"Fork\" button). 2. Clone your fork locally: git clone git@github.com:YOURGITHUBNAME/python-tblib.git 3. Create a branch for local development: git checkout -b name-of-your-bugfix-or-feature Now you can make your changes locally. 4. When you\'re done making changes run all the checks and docs builder with one command: tox 5. Commit your changes and push your branch to GitHub: git add . git commit -m "Your detailed description of your changes." git push origin name-of-your-bugfix-or-feature 6. Submit a pull request through the GitHub website. ### Pull Request Guidelines If you need some code review or feedback while you\'re developing the code just make the pull request. For merging, you should: 1. Include passing tests (run `tox`). 2. Update documentation when there\'s new API, functionality etc. 3. Add a note to `CHANGELOG.rst` about the changes. 4. Add yourself to `AUTHORS.rst`. ### Tips To run a subset of tests: tox -e envname -- pytest -k test_myfeature To run all the test environments in *parallel*: tox -p auto
Repo symbol

tblib repository

Repo symbol

tblib repository