Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

Support pyenv package manager #22225

Open
rarkins opened this issue May 15, 2023 · 1 comment
Open

Support pyenv package manager #22225

rarkins opened this issue May 15, 2023 · 1 comment
Labels
new package manager New package manager support priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:feature Feature (new functionality)

Comments

@rarkins
Copy link
Collaborator

rarkins commented May 15, 2023

What would you like Renovate to be able to do?

Support Renovating pyenv's .python.version file.

If you have any ideas on how this should be implemented, please tell us here.

Should be similar to .nvmrc file handling, although unlike that pyenv can support multiple versions.

Source: https://github.com/pyenv/pyenv

Relevant: "You can also specify multiple versions in a .python-version file by hand, separated by newlines."

Is this a feature you are interested in implementing yourself?

No
@rarkins rarkins added type:feature Feature (new functionality) priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others new package manager New package manager support status:requirements Full requirements are not yet known, so implementation should not be started labels May 15, 2023
@github-actions
Copy link
Contributor

Hi there,

You're asking us to support a new package manager. We need to know some basic information about this package manager first. Please copy/paste the new package manager questionnaire, and fill it out in full.

Once the questionnaire is filled out we'll decide if we want to support this new manager.

Good luck,

The Renovate team

@rarkins rarkins added status:ready priority-4-low Low priority, unlikely to be done unless it becomes important to more people and removed status:requirements Full requirements are not yet known, so implementation should not be started priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others labels Oct 1, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
new package manager New package manager support priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:feature Feature (new functionality)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rarkins