mirror of
https://github.com/pyenv/pyenv.git
synced 2026-09-10 07:36:16 -04:00
- rbenv compatibility note
We've not been syncing with Rbenv for years
This commit is contained in:
parent
8771e721c1
commit
2bd4f6c4da
3
.github/PULL_REQUEST_TEMPLATE.md
vendored
3
.github/PULL_REQUEST_TEMPLATE.md
vendored
|
|
@ -3,9 +3,6 @@ Make sure you have checked all steps below.
|
||||||
### Prerequisite
|
### Prerequisite
|
||||||
* [ ] Please consider implementing the feature as a hook script or plugin as a first step.
|
* [ ] Please consider implementing the feature as a hook script or plugin as a first step.
|
||||||
* pyenv has some powerful support for plugins and hook scripts. Please refer to [Authoring plugins](https://github.com/pyenv/pyenv/wiki/Authoring-plugins) for details and try to implement it as a plugin if possible.
|
* pyenv has some powerful support for plugins and hook scripts. Please refer to [Authoring plugins](https://github.com/pyenv/pyenv/wiki/Authoring-plugins) for details and try to implement it as a plugin if possible.
|
||||||
* [ ] Please consider contributing the patch upstream to [rbenv](https://github.com/rbenv/rbenv), since we have borrowed most of the code from that project.
|
|
||||||
* We occasionally import the changes from rbenv. In general, you can expect changes made in rbenv will be imported to pyenv too, eventually.
|
|
||||||
* Generally speaking, we prefer not to make changes in the core in order to keep compatibility with rbenv.
|
|
||||||
* [ ] My PR addresses the following pyenv issue (if any)
|
* [ ] My PR addresses the following pyenv issue (if any)
|
||||||
- Closes https://github.com/pyenv/pyenv/issues/XXXX
|
- Closes https://github.com/pyenv/pyenv/issues/XXXX
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue