Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: use an example black version that does not explode #18270

Merged
merged 1 commit into from
Feb 16, 2023
Merged

docs: use an example black version that does not explode #18270

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/markdown/Python/python-goals/python-package-goal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ Usually, you'll want to use `entry_point`, which lets you specify a module and o

```
❯ ./dist/black.pex --version
python -m black, version 21.10b0
python -m black, 23.1.0 (compiled: yes)
```

You can also leave off both fields, which will cause `./dist/my_app.pex` to launch a Python interpreter with all the relevant code and dependencies loaded.
Expand Down Expand Up @@ -126,7 +126,7 @@ Unlike using `entry_point` with a file name, this does not work with file argume
You can set the `script` to any `console_script` or script exposed by your third-party requirements.

```python helloworld/BUILD
python_requirement(name="black_req", requirements=["black==21.10b0"])
python_requirement(name="black_req", requirements=["black==23.1.0"])

pex_binary(
name="black_bin",
Expand Down