Skip to content
Deployment failed during build process
niklasbaumgardner
OP

2 years ago

Collecting SQLAlchemy-serializer==1.4.12 (from -r requirements.txt (line 49))
  Downloading SQLAlchemy-serializer-1.4.12.tar.gz (16 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
  ╰─> [31 lines of output]
      Traceback (most recent call last):
        File "/opt/venv/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/opt/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 "/opt/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-eoqm9_4j/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-eoqm9_4j/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 304, in _get_build_requires
          self.run_setup()
        File "/tmp/pip-build-env-eoqm9_4j/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-eoqm9_4j/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 320, in run_setup
          exec(code, locals())
        File "<string>", line 7, in <module>
        File "/tmp/pip-build-env-eoqm9_4j/overlay/lib/python3.12/site-packages/setuptools/__init__.py", line 116, in setup
          _install_setup_requires(attrs)
        File "/tmp/pip-build-env-eoqm9_4j/overlay/lib/python3.12/site-packages/setuptools/__init__.py", line 87, in _install_setup_requires
          dist.parse_config_files(ignore_option_errors=True)
        File "/tmp/pip-build-env-eoqm9_4j/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-eoqm9_4j/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-eoqm9_4j/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), please use the underscore name 'description_file' instead.
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Solved

4 Replies

chandrika
EMPLOYEE

2 years ago

Hey there, looks like the error mentions that you might need to use the correct file name:

File "/tmp/pip-build-env-eoqm9_4j/overlay/lib/python3.12/site-packages/setuptools/dist.py", line 629, in enforceunderscore raise InvalidConfigError( setuptools.errors.InvalidConfigError: Invalid dash-separated key 'description-file' in 'metadata' (setup.cfg), please use the underscore name 'description_file' instead. [end of output]

Could you update that and see if it helps?


Status changed to Awaiting User Response Railway • over 1 year ago


niklasbaumgardner
OP

2 years ago

The build was working yesterday and I haven't changed any file names or updated any dependencies.


Status changed to Awaiting Railway Response Railway • over 1 year ago


niklasbaumgardner
OP

2 years ago

The issue was some pip dependency. I'm not exactly sure what caused the issue but upgrading all of my pip packages fixed the issue.


chandrika
EMPLOYEE

2 years ago

Yeah, sounds like there might've been a dependency conflict or a bug in one of the packages that was fixed in a newer version. Glad this is sorted and feel free to reach out if you have any more questions or run into further issues!


Status changed to Awaiting User Response Railway • over 1 year ago


Status changed to Solved chandrika • over 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...