You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
ORPA-pyOpenRPA/Resources/WPy64-3720/python-3.7.2.amd64/Lib/site-packages/bleach/_vendor
root ee22027d4f
fix rights to 755 (linux actual)
2 years ago
..
html5lib fix rights to 755 (linux actual) 2 years ago
html5lib-1.0.1.dist-info fix rights to 755 (linux actual) 2 years ago
README.rst fix rights to 755 (linux actual) 2 years ago
__init__.py fix rights to 755 (linux actual) 2 years ago
pip_install_vendor.sh fix rights to 755 (linux actual) 2 years ago
vendor.txt fix rights to 755 (linux actual) 2 years ago

README.rst

=======================
Vendored library policy
=======================

To simplify Bleach development, we're now vendoring certain libraries that
we use.

Vendored libraries must follow these rules:

1. Vendored libraries must be pure Python--no compiling.
2. Source code for the libary is included in this directory.
3. License must be included in this repo and in the Bleach distribution.
4. Requirements of the library become requirements of Bleach.
5. No modifications to the library may be made.


Adding/Updating a vendored library
==================================

Way to vendor a library or update a version:

1. Update ``vendor.txt`` with the library, version, and hash. You can use 
   `hashin <https://pypi.org/project/hashin/>`_.
2. Remove all old files and directories of the old version.
3. Run ``pip_install_vendor.sh`` and check everything it produced in including
   the ``.dist-info`` directory and contents.


Reviewing a change involving a vendored library
===============================================

Way to verify a vendored library addition/update:

1. Pull down the branch.
2. Delete all the old files and directories of the old version.
3. Run ``pip_install_vendor.sh``.
4. Run ``git diff`` and verify there are no changes.