
There are two standalone markdown-parsing tools in the repo, one in //tools/md_browser and the other in //net/tools/net_docs. Each uses a checked-in third-party copy of the Python markdown library (two different versions). Best practice these days for handling third-party packages of Python code is to use CIPD if you can; this tightens up the provenance better, hides the dependencies from the calling code, and allows the calling code to just import the library directly without doing any sys.path hacking. We can't use CIPD to remove both uses of the library, as one of the two uses happens during the build, and we're not allowed to use vpython as a build action. This change is motivated by crbug.com/14038, where we upgraded //third_party/Python-Markdown from v3.3.4 to v3.4.1, but we missed that the new version added a dependency on `importlib-metadata`. Using CIPD packages would've caught that. This CL switches md_browser to use vpython and CIPD, and removes one of the two checked-in copies. Bug: 140398 Change-Id: I583603e4c1318019b1b15391f52f989f4f8545f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4283145 Reviewed-by: Ben Pastene <bpastene@chromium.org> Reviewed-by: Bruce Dawson <brucedawson@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Cr-Commit-Position: refs/heads/main@{#1109359}
Chromium
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead,
follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.