Without it, the error message is not clear from the get go and we need to tamper with
build configuration to actually have access to the error message.
See [1] with the --verbose flag versus [2] without it.
[1]
17:56:44 [?25h[34mINFO [0m Response from https://upload.pypi.org/legacy/: 17:56:44 400 The description failed to render for 'text/x-rst'. See 17:56:44 https://pypi.org/help/#description-content-type for more information. 17:56:44 [34mINFO [0m <html> 17:56:44 <head> 17:56:44 <title>400 The description failed to render for 'text/x-rst'. See 17:56:44 https://pypi.org/help/#description-content-type for more 17:56:44 information.</title> 17:56:44 </head> 17:56:44 <body> 17:56:44 <h1>400 The description failed to render for 'text/x-rst'. See 17:56:44 https://pypi.org/help/#description-content-type for more 17:56:44 information.</h1> 17:56:44 The server could not comply with the request since it is either 17:56:44 malformed or otherwise incorrect.<br/><br/> 17:56:44 The description failed to render for 'text/x-rst'. See 17:56:44 https://pypi.org/help/#description-content-type for more information. 17:56:44 17:56:44 17:56:44 </body> 17:56:44 </html>
from https://jenkins.softwareheritage.org/job/DLDCVS/job/pypi-upload/12/console
[2]
17:44:19 [?25h[33mWARNING [0m Error during upload. Retry with the --verbose option for more details.
https://jenkins.softwareheritage.org/job/DLDCVS/job/pypi-upload/11/console