| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Mention limitation in editable docs | Anderson Bravalheri | 2023-02-17 | 1 | -0/+5 |
| | | |||||
| * | Update note about SETUPTOOLS_ENABLE_FEATURES | Anderson Bravalheri | 2023-02-13 | 1 | -15/+6 |
| | | |||||
| *-. | Merge spelling/space improvements (#3695, #3698, #3697, #3699) | Anderson Bravalheri | 2022-11-23 | 1 | -3/+3 |
| |\ \ | |||||
| | | * | Fix non-ASCII homoglyph of `v` | Dimitri Papadopoulos | 2022-11-21 | 1 | -1/+1 |
| | |/ |/| | |||||
| | * | Fix typos found by codespell | Dimitri Papadopoulos | 2022-11-20 | 1 | -2/+2 |
| |/ | |||||
| * | Minor stylistic change | Anderson Bravalheri | 2022-11-11 | 1 | -1/+2 |
| | | |||||
| * | Fix typo in docs/userguide/development_mode.rst | shripadbadithe | 2022-11-06 | 1 | -2/+1 |
| | | |||||
| * | Fix misspelling in docs/userguide/development_mode.rst | Anderson Bravalheri | 2022-10-11 | 1 | -1/+1 |
| | | |||||
| * | Document CWD limitations in editable docs | Anderson Bravalheri | 2022-08-26 | 1 | -0/+11 |
| | | |||||
| * | Correct docs on how to use the `legacy-editable` mode | Ed Morley | 2022-08-17 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | PR #3414 added support for disabling the new PEP660 editable install hooks. However the documentation and changelog mentions didn't match the implementation. Before: - The implementation used: `SETUPTOOLS_ENABLE_FEATURES` - The changelog said to use: `SETUPTOOLS_ENABLE_FEATURE` (notice the missing "S") - The docs said to use: `SETUPTOOLS_USE_FEATURE` This caused confusion in #3535, since the testcase there used the form mentioned in the changelog, which doesn't do anything. Now, the changelog and docs both say to use `SETUPTOOLS_ENABLE_FEATURES`. | ||||
| * | typo fix | wim glenn | 2022-08-13 | 1 | -1/+1 |
| | | |||||
| * | Remove question mark | Mike Hucka | 2022-08-12 | 1 | -2/+2 |
| | | | | The heading "How editable installations work?" either contains a typo (the question mark should be omitted), or else the question as written is missing a word (it should be "How **do** editable installations work?"). This commit removes the question mark. | ||||
| * | Typo in user guide: development mode | Louis Maddox | 2022-08-12 | 1 | -1/+1 |
| | | | | `PATHONPATH` --> `PYTHONPATH` | ||||
| * | docs: Avoid refering to the strict mode as experimental | Anderson Bravalheri | 2022-08-11 | 1 | -1/+2 |
| | | |||||
| * | docs: Fix incorrect syntax | Anderson Bravalheri | 2022-08-05 | 1 | -1/+1 |
| | | |||||
| * | docs: Fix phrases in userguide/development_mode | Anderson Bravalheri | 2022-08-05 | 1 | -2/+2 |
| | | |||||
| * | docs: Fix link display text | Anderson Bravalheri | 2022-08-04 | 1 | -1/+1 |
| | | |||||
| * | docs: Improve developement_mode.rst | Anderson Bravalheri | 2022-08-03 | 1 | -8/+10 |
| | | |||||
| * | doc: Add section explaining how editable installs work | Anderson Bravalheri | 2022-08-03 | 1 | -0/+44 |
| | | |||||
| * | docs: Mention 'compat' editable installation mode | Anderson Bravalheri | 2022-08-03 | 1 | -2/+29 |
| | | |||||
| * | docs: Expand editable install limitations section | Anderson Bravalheri | 2022-08-03 | 1 | -1/+23 |
| | | |||||
| * | Fix outdated version number in docsv64.0.0b1 | Anderson Bravalheri | 2022-07-04 | 1 | -2/+2 |
| | | |||||
| * | Document dir in strict editable installs | Anderson Bravalheri | 2022-06-29 | 1 | -0/+9 |
| | | |||||
| * | Add notes about namespaces, tox + small fixes | Anderson Bravalheri | 2022-06-27 | 1 | -8/+13 |
| | | |||||
| * | Add note about using editable installs for test environments | Anderson Bravalheri | 2022-06-25 | 1 | -0/+6 |
| | | |||||
| * | Allow users to opt-into previous "develop" behavior | Anderson Bravalheri | 2022-06-25 | 1 | -0/+12 |
| | | |||||
| * | Update development mode docs | Anderson Bravalheri | 2022-06-25 | 1 | -31/+129 |
| | | |||||
| * | Removed quotes around Development Mode. | Saniya Maheshwari | 2022-06-23 | 1 | -2/+2 |
| | | |||||
| * | Apply suggestions from code review | Anderson Bravalheri | 2022-06-13 | 1 | -2/+2 |
| | | |||||
| * | Improve docs by avoiding confusion with distutils | Anderson Bravalheri | 2022-06-12 | 1 | -32/+14 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The existing docs seem to assume that the user is familiar with the history of packaging in the Python ecosystem (or at least know what is `distutils`). Since that is not always the case and that `distutils` is in the process of being adopted by `setuptools`, the documentation should be changed to minimize mentions to `distutils` and avoid expecting too much knowledge from the users. The benefit of this approach is that it can make the docs more accessible and easier to understand. Changes: - Modify landing page to clarify what `setuptools` does (making it more clear to understand for beginners). - Remove mentions to `distutils`, `transition to PEP 517` from `userguide/index`. - Instead the text is changed to have a more "introductory" tone. - Remove mentions to `distutils` from the Quickstart. - Remove `python2` from the intersphinx mapping - it was causing trouble redirecting glossary terms to Python2 docs, instead of Python3. - Modify documentation about development mode to be more aligned with current practices (i.e. using `pip install -e .`) - In this process all documentation about running `setuptools` commands in `distutils` projects was moved to a new file in `docs/deprecated/running_commands.rst` | ||||
| * | remove lib2to3 usage | Thomas Grainger | 2021-09-04 | 1 | -8/+0 |
| | | |||||
| * | Clarify Development Mode first paragraph | Daniel Moore | 2020-12-23 | 1 | -3/+3 |
| | | |||||
| * | 📝 Recover interdoc links & correct broken syntax | Sviatoslav Sydorenko | 2020-10-16 | 1 | -2/+2 |
| | | |||||
| * | Use canonical extension for docs. | Jason R. Coombs | 2020-09-23 | 1 | -0/+60 |
 |
index : delta/python-setuptools-git.git | |
| github.com: pypa/setuptools.git |
| summaryrefslogtreecommitdiff |