Invalid dash-separated key 'description-file' in 'metadata' (setup.cfg)

[wrr]

I'm using python-postmark successfully for many years, thank your for your great work! Recently, while trying to install it on a machine with Python 3.12.3 and pip 25.01, I'm getting the following installation error:

Collecting python-postmark==0.6.0 (from -r requirements.txt (line 12))
 Using cached python-postmark-0.6.0.tar.gz (11 kB)
 Installing build dependencies: started
 Installing build dependencies: finished with status 'done'
 Getting requirements to build wheel: started
 Getting requirements to build wheel: finished with status 'error'
 error: subprocess-exited-with-error
 
 × Getting requirements to build wheel did not run successfully.
 │ exit code: 1
 ╰─> [29 lines of output]
     Traceback (most recent call last):
       File "/home/alice/project/venv/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
         main()
       File "/home/alice/project/venv/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
         json_out['return_val'] = hook(**hook_input['kwargs'])
                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       File "/home/alice/project/venv/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
         return hook(config_settings)
                ^^^^^^^^^^^^^^^^^^^^^
       File "/tmp/pip-build-env-_oweoi4l/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 334, in get_requires_for_build_wheel
         return self._get_build_requires(config_settings, requirements=[])
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       File "/tmp/pip-build-env-_oweoi4l/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 304, in _get_build_requires
         self.run_setup()
       File "/tmp/pip-build-env-_oweoi4l/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 522, in run_setup
         super().run_setup(setup_script=setup_script)
       File "/tmp/pip-build-env-_oweoi4l/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 320, in run_setup
         exec(code, locals())
       File "<string>", line 9, in <module>
       File "/tmp/pip-build-env-_oweoi4l/overlay/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 160, in setup
         dist.parse_config_files()
       File "/tmp/pip-build-env-_oweoi4l/overlay/lib/python3.12/site-packages/setuptools/dist.py", line 730, in parse_config_files
         self._parse_config_files(filenames=inifiles)
       File "/tmp/pip-build-env-_oweoi4l/overlay/lib/python3.12/site-packages/setuptools/dist.py", line 599, in _parse_config_files
         opt = self._enforce_underscore(opt, section)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       File "/tmp/pip-build-env-_oweoi4l/overlay/lib/python3.12/site-packages/setuptools/dist.py", line 629, in _enforce_underscore
         raise InvalidConfigError(
     setuptools.errors.InvalidConfigError: Invalid dash-separated key 'description-file' in 'metadata' (setup.cfg)3, please use the underscore name 'description_file' instead.

Brief search indicates that the deprecation of keys with dashes (description-file) in favor of underscore (description_file) has become a hard error with newer setuptools. I'm not very knowledgeable of the Python setuptools in general, so I'm not sure if changing the key could cause problems for users that use old setuptools. Based on a brief search, description-file isn't a widely used setting, and perhaps could be removed altogether?

[twentyforty]

Im also running into this.

[twentyforty]

theres already a pull request. #121

[nicholasserra]

I'll get this fixed and released today thank you

[twentyforty]

Thank you!

…

On Mon, Mar 24, 2025 at 3:38 PM Nicholas Serra ***@***.***> wrote: I'll get this fixed and released today thank you — Reply to this email directly, view it on GitHub <#122 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQKP5HLWNLKNOCR72VQHRT2WBNMJAVCNFSM6AAAAABZVSP4RWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBZGIYTCMBVGY> . You are receiving this because you commented.Message ID: ***@***.***> [image: nicholasserra]*nicholasserra* left a comment (themartorana/python-postmark#122) <#122 (comment)> I'll get this fixed and released today thank you — Reply to this email directly, view it on GitHub <#122 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQKP5HLWNLKNOCR72VQHRT2WBNMJAVCNFSM6AAAAABZVSP4RWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBZGIYTCMBVGY> . You are receiving this because you commented.Message ID: ***@***.***>

[nicholasserra]

Just pushed 0.6.1. I was not able to replicate the issue on my machine. So, if someone can give it a whirl and confirm fix, that would be awesome

https://pypi.org/project/python-postmark/0.6.1/

[mdotmoment11]

That fixed the build, but now, when I try to send, I get:

TypeError: Client.init() got an unexpected keyword argument 'proxy'

Seems to be an issue with the underlying http.client package.

[nicholasserra]

Odd, sounds like something in your implementation @mdotmoment11, nothing else changed. Lemme see if anyone else chimes in here.

[nicholasserra]

Just did a basic PMMail send on my end and worked.

[mdotmoment11]

Odd, sounds like something in your implementation @mdotmoment11, nothing else changed. Lemme see if anyone else chimes in here.

I'm running your package up on GCP in Cloud Run. Seems there was a change in the underlying http.client package they use. I downgraded httpx to 0.27.2 and all is well