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.

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

Custom prefix in .ini source #2927

Merged
merged 3 commits into from
Feb 21, 2023
Merged

Custom prefix in .ini source #2927

merged 3 commits into from
Feb 21, 2023

Conversation

masenf
Copy link
Collaborator

@masenf masenf commented Feb 21, 2023

Fix bug #2926.

For plugin developers to have more flexibility when loading configuration from tox.ini using the mechanisms provided by tox.

As an implementation note: I've tried to keep the door open for future support of generative environments for custom prefixes (factors) as well. it's not publicly plumbed through at the moment, but in the future, if the _section_mapping contained custom keys (perhaps expanded according to plugin logic), then it could auto-dispatch to a base environment just like a generative testenv does.

Thanks for contribution

Please, make sure you address all the checklists (for details on how see
development documentation)!

  • ran the linter to address style issues (tox -e fix)
  • wrote descriptive pull request text
  • ensured there are test(s) validating the fix
  • added news fragment in docs/changelog folder
  • updated/extended the documentation

ensure that loaders returned from .ini source are bound
to the correct section prefix, if specified.

add comment explaining why the code must look up the name
in the _section_mapping

fix tox-dev#2926
@gaborbernat gaborbernat merged commit f4fcb7b into tox-dev:main Feb 21, 2023
@gaborbernat
Copy link
Member

@masenf can you cut a release? Just run tox -e release -- version to trigger it. and then the CI will do the rest 😅 you can manually cut a GitHub release against the generated git tag as a final step.

@masenf
Copy link
Collaborator Author

masenf commented Feb 22, 2023

I need to learn to make releases sooner or later. Looks like you already handled 4.4.6 before I had a chance to pick it up. I'll try to get the next one, just to learn how it works.

@masenf masenf deleted the custom_prefix branch February 22, 2023 05:53
descope bot referenced this pull request in descope/django-descope Mar 7, 2023
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [tox](https://togithub.com/tox-dev/tox)
([changelog](https://tox.wiki/en/latest/changelog.html)) | dev | patch |
`4.4.5` -> `4.4.6` |

---

### Release Notes

<details>
<summary>tox-dev/tox</summary>

### [`v4.4.6`](https://togithub.com/tox-dev/tox/releases/tag/4.4.6)

[Compare Source](https://togithub.com/tox-dev/tox/compare/4.4.5...4.4.6)

#### What's Changed

- Add link to our own disucssion board by
[@&#8203;jugmac00](https://togithub.com/jugmac00) in
[https://github.com/tox-dev/tox/pull/2921](https://togithub.com/tox-dev/tox/pull/2921)
- Custom prefix in .ini source by
[@&#8203;masenf](https://togithub.com/masenf) in
[https://github.com/tox-dev/tox/pull/2927](https://togithub.com/tox-dev/tox/pull/2927)

**Full Changelog**: tox-dev/tox@4.4.5...4.4.6

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC4xMDEuMCIsInVwZGF0ZWRJblZlciI6IjM0LjEwMS4wIn0=-->

Co-authored-by: descope[bot] <descope[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants