Nie możesz wybrać więcej, niż 25 tematów Tematy muszą się zaczynać od litery lub cyfry, mogą zawierać myślniki ('-') i mogą mieć do 35 znaków.

21 wiersze
1.5 KiB

  1. Too many issues will kill our team's development velocity, drastically.
  2. Make sure you have checked all steps below.
  3. ### Prerequisite
  4. * [ ] Make sure your problem is not listed in [the common build problems](https://github.com/pyenv/pyenv/wiki/Common-build-problems).
  5. * [ ] Make sure no duplicated issue has already been reported in [the pyenv issues](https://github.com/pyenv/pyenv/issues). You should look for closed issues, too.
  6. * [ ] Make sure you are not asking us to help solving your specific issue.
  7. * GitHub issues is opened mainly for development purposes. If you want to ask someone to help solving your problem, go to some community site like [Gitter](https://gitter.im/yyuu/pyenv), [StackOverflow](https://stackoverflow.com/questions/tagged/pyenv), etc.
  8. * [ ] Make sure your problem is not derived from packaging (e.g. [Homebrew](https://brew.sh)).
  9. * Please refer to the package documentation for the installation issues, etc.
  10. * [ ] Make sure your problem is not derived from plugins.
  11. * This repository is maintaining `pyenv` and the default `python-build` plugin only. Please refrain from reporting issues of other plugins here.
  12. ### Description
  13. - [ ] Platform information (e.g. Ubuntu Linux 16.04):
  14. - [ ] OS architecture (e.g. amd64):
  15. - [ ] pyenv version:
  16. - [ ] Python version:
  17. - [ ] C Compiler information (e.g. gcc 7.3):
  18. - [ ] Please attach verbose build log as gist
  19. * You can turn on verbose debug logging using by setting `PYENV_DEBUG=1`, e.g. `env PYENV_DEBUG=1 pyenv install -v 3.6.4`