[issue14778] logging messages about bad version numbers should include the project name

Éric Araujo added the comment: distutils2 development has stopped. -- resolution: -> out of date stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker _

[issue14778] logging messages about bad version numbers should include the project name

Changes by Christoph Sieghart : Added file: http://bugs.python.org/file25589/bad_version_number_with_name.patch ___ Python tracker ___ ___ Pyt

[issue14778] logging messages about bad version numbers should include the project name

Changes by Christoph Sieghart : Removed file: http://bugs.python.org/file25587/bad_version_number_with_name.patch ___ Python tracker ___ ___

[issue14778] logging messages about bad version numbers should include the project name

Christoph Sieghart added the comment: I wrote a trivial patch against the CPython repository that adds the name to the exception message. Did I forget anything? What kind of test would make sense? -- keywords: +patch Added file: http://bugs.python.org/file25587/bad_version_number_with

[issue14778] logging messages about bad version numbers should include the project name

Christoph Sieghart added the comment: The optional argument approach doesn't seem clean to me either. I think the correct approach is - as you wrote - to change the higher level code to include the project name in the exception message. -- ___ Pyt

[issue14778] logging messages about bad version numbers should include the project name

Éric Araujo added the comment: BTW there could be an optional argument in the exception constructor for the project name, but that does not seem clean to me. -- title: IrrationalVersionError should include the project name -> logging messages about bad version numbers should include t