regebro/pyroma

Issues

• Support PEP 639 license metadata once that PEP is accepted

  #93 opened 2 years ago by edmorley
  8

• Have Pyroma detect and report better error for non-UTF-8 encoded license file?

  #76 opened 2 months ago by mcflugen
  2

• Allow private classifier

  #101 opened 2 years ago by gforcada
  2

• pyroma fails in the pre-commit.ci

  #102 opened 2 months ago by mkryvy-cb
  1

• Incompatible with Python 3.12

  #104 opened a year ago by mweinelt
  0

• Add new check: package-name should correspond uniquely to module-name

  #100 opened 2 years ago by woutervh
  6

• Suggestion: Support private PyPI servers

  #46 opened 5 years ago by Liam-Deacon
  1

• check-manifest integration / merge

  #1 opened 2 years ago by regebro
  5

• Disable checks

  #69 opened 2 years ago by kasium
  6

• My meta data is not recognized

  #94 opened 2 years ago by buhtz
  10

• 4.1: test_custom_test and test_minimal fails

  #95 opened 2 years ago by mtelka
  2

• Support poetry

  #64 opened 2 years ago by woutervh
  5

• Official document (PEP?) your tests are based on?

  #96 opened 2 years ago by buhtz
  2

• conda-forge link is broken

  #63 opened 3 years ago by asears
  2

• Upload wheel to PyPI

  #91 opened 2 years ago by hugovk
  1

• Future plans

  #75 opened 3 years ago by regebro
  11

• Pyroma reports 'Your package does not have author data' when author is in fact specified in pyproject.toml

  #77 opened 2 years ago by bessman
  5

• Check `python_requires` for supported python version (PEP 440)

  #82 opened 2 years ago by davidandreoletti
  8

• Pyroma outputs verbose build backend output when building metadata

  #86 opened 2 years ago by wesleybl
  8

• Broken with current setuptools version?

  #71 opened 3 years ago by icemac
  11

• Redundant messages when no version is specified

  #70 opened 3 years ago by kasium
  1

• Exit code for CI

  #68 opened 3 years ago by kasium
  3

• Tests failure on Python 3.7

  #65 opened 3 years ago by fabaff
  0

• Checking packages from PyPI appears to be broken

  #55 opened 4 years ago by CAM-Gerlach
  15

• Suggestion: quiet output for providing just the score

  #47 opened 4 years ago by Liam-Deacon
  2

• Pyroma doesn't work on Windows 10

  #28 opened 4 years ago by sandeepbhat
  6

• Accept markdown long descriptions

  #42 opened 5 years ago by JulienPalard
  5

• Missing pygments dependency in setup.py

  #41 opened 5 years ago by vpoulailleau
  1

• [Question] Continuous integration behavior

  #16 opened 6 years ago by Kristinita
  5

• Don't mark down when known Trove licence present +`license` omitted

  #38 opened 6 years ago by hugovk
  1

• pyroma changes sys.argv, and restoring fails

  #35 opened 6 years ago by mauritsvanrees
  0

• [Question] zip_safe setting if Wheels

  #19 opened 6 years ago by Kristinita
  4

• pyroma should not warn about license if the license is specified in classifiers

  #29 opened 6 years ago by akitada
  2

• The long_description ReST test passes even if it's not valid ReST

  #31 opened 6 years ago by regebro
  0

• More checks

  #2 opened 6 years ago by regebro
  7

• Start suggesting people add `project_urls` to setup.py

  #21 opened 6 years ago by mgedmin
  2

• Check for Development Status classifier

  #26 opened 6 years ago by davidak
  1

• [Feature request] Continuous integration support

  #15 opened 6 years ago by Kristinita
  2

• Add Development Status classifier

  #25 opened 6 years ago by davidak
  1

• Pyroma failing to start due to pypi page changes.

  #23 opened 6 years ago by Alphadelta14
  1

• DeprecationWarnings in Python 3

  #22 opened 7 years ago by hugovk
  1

• Pyroma installation fails if LC_ALL is set to en_US.ascii

  #12 opened 7 years ago by ericof
  4

• Fails to install on CircleCI

  #14 opened 7 years ago by Martmists-GH
  2

• Accept alternate readthedocs.org domain names

  #3 opened 7 years ago by paternal
  1

• Parsing error `<string>:1: (WARNING/2) Inline strong start-string without end-string.`

  #9 opened 7 years ago by Aluriak
  2