1. 03 2月, 2022 1 次提交
  2. 07 12月, 2021 2 次提交
  3. 25 6月, 2020 1 次提交
    • B
      Add JetBrains note for PyCharm to Python.gitignore · 22f1ff9a
      BrianMSheldon 提交于
      First and foremost I think that requiring such a complicated gitignore for JetBrains IDEs is a failure on JetBrains part in structuring their project setting.  I also feel that it should be included in the `Python.gitignore` due to its popularity and due to the frequency of requests.  A quick search for `PyCharm` PRs shows 81 closed PRs requesting it be added and if searching for `.idea` you can see many more have been requested.  However I understand the maintenance burden in including it when a user can manually merge the two files themselves so I understand why the maintainers have opted to maintain it seperately.  
      
      The main problem I see is that with many people adding the `Python.gitignore` at project creation through the Github UI and the `JetBrains.gitignore` being in the Global folder and makes it less discoverable than it should be.  
      
      This PR adds a comment for people adding the `Python.gitignore` directing them to the global `JetBrains.gitignore` which should solve this issue in a way that is acceptable for the maintainers, since comment-only sections already exist for `pyenv` and `pipenv`.
      22f1ff9a
  4. 12 4月, 2020 1 次提交
  5. 05 4月, 2020 1 次提交
  6. 13 3月, 2020 2 次提交
  7. 11 3月, 2020 1 次提交
    • E
      Ignore Cython debug symbols (#3330) · 589831e1
      Elijah Shaw-Rutschman 提交于
      Cython extension modules built with `gdb_debug=True` spit out debug symbols in the `cython_debug` directory at the top level of the project. The files in this directory contain hardcoded paths and are not shareable/meaningful across environments, so I think it makes sense to include them in a default Python .gitignore.
      589831e1
  8. 20 2月, 2020 1 次提交
  9. 10 2月, 2020 2 次提交
  10. 18 11月, 2019 1 次提交
  11. 09 11月, 2019 2 次提交
  12. 20 9月, 2019 1 次提交
  13. 26 5月, 2019 1 次提交
  14. 09 5月, 2019 1 次提交
  15. 11 3月, 2019 1 次提交
    • J
      Add ignore rules for Pipenv (#2977) · 7079791a
      Jarry Shaw 提交于
      * Add ignore rules for Pipenv
      
      Pipenv uses Pipfile.lock to maintain Python package information
      (metadata, hash, etc.) installed as described in Pipfile. Thus,
      Pipfile.lock may vary on different operating systems, platforms
      when collaborating. This PR adds Pipfile.lock into the Python
      default gitignore. See http://pipenv.org
      
      * Update Python.gitignore
      
      Not to ignore Pipfile.lock in default, but explain
      when and why it should be ignored in case of
      collaboration. (adjusted according to comment
      in github/gitignore#2977 by @drothmaler )
      
      * Apply suggestions from code review
      Co-Authored-By: NJarryShaw <jarryshaw@icloud.com>
      
      * Update Python.gitignore
      
      As suggested by @shiftkey , elaborate on the problems that users might see with `Pipfile.lock`.
      7079791a
  16. 26 1月, 2019 1 次提交
  17. 10 11月, 2018 1 次提交
  18. 23 10月, 2018 1 次提交
  19. 10 9月, 2018 1 次提交
  20. 27 8月, 2018 1 次提交
  21. 22 8月, 2018 1 次提交
  22. 19 8月, 2018 3 次提交
  23. 25 2月, 2018 1 次提交
  24. 04 2月, 2018 1 次提交
  25. 12 1月, 2018 1 次提交
  26. 29 8月, 2017 1 次提交
  27. 21 6月, 2017 2 次提交
  28. 26 5月, 2017 1 次提交
    • S
      add MANIFEST to Python.gitignore · 6d5d7e0c
      Shiwei Sun 提交于
      add MANIFEST which is GENERATED by distutils
      
      Reasons for making this change:
      
      if you use distutils.core to setup, the file MANIFEST is generated by distutils when run 'python setup.py sdist'
      6d5d7e0c
  29. 22 5月, 2017 1 次提交
    • J
      Consolidate all environments in one section · 252058ed
      jwg4 提交于
      Some of these names relate to specific tools, others could be used by multiple tools. In particular, virtualenv, the most popular tool for creating Python environments, does not mandate any of these and venv/ or .venv are simply conventional. It is more readable to group all of these together.
      252058ed
  30. 12 5月, 2017 1 次提交
  31. 07 5月, 2017 1 次提交
  32. 01 4月, 2017 1 次提交
  33. 31 3月, 2017 1 次提交