Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

setuptools removal breaking builds #247

Copy link
Copy link
Closed as not planned
Closed as not planned
Copy link
@ipmb

Description

@ipmb
Issue body actions

I've seen numerous builds that were previously working and now fail since v0.14.0 was released with #243

Many have a requirements.txt generated using pip-tools --generate-hashes ... without using the --allow-unsafe flag.

This results in errors like this at build time:

Collecting setuptools (from pip-tools==6.13.0->-r requirements.txt (line 1169))
ERROR: In --require-hashes mode, all requirements must have their versions pinned with ==. These do not:
    setuptools from https://files.pythonhosted.org/packages/e1/58/e0ef3b9974a04ce9cde2a7a33881ddcb2d68450803745804545cdd8d258f/setuptools-72.1.0-py3-none-any.whl (from pip-tools==6.13.0->-r requirements.txt (line 1169))

[Error: Unable to install dependencies using pip]
The 'pip install' command to install the application's dependencies from
'requirements.txt' failed (exit status: 1).

See the log output above for more information.

ERROR: failed to build: exit status 1
ERROR: failed to build: executing lifecycle: failed with status code: 51

Some packages have implicit dependencies on setuptools. Here's an example of an error I just saw:

Traceback (most recent call last):
  File "/workspace/manage.py", line 23, in <module>
    main()
  File "/workspace/manage.py", line 19, in main
    execute_from_command_line(sys.argv)
  File "/layers/heroku_python/dependencies/lib/python3.11/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line
    utility.execute()
  File "/layers/heroku_python/dependencies/lib/python3.11/site-packages/django/core/management/__init__.py", line 420, in execute
    django.setup()
  File "/layers/heroku_python/dependencies/lib/python3.11/site-packages/django/__init__.py", line 24, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/layers/heroku_python/dependencies/lib/python3.11/site-packages/django/apps/registry.py", line 91, in populate
    app_config = AppConfig.create(entry)
                 ^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.11/site-packages/django/apps/config.py", line 126, in create
    mod = import_module(mod_path)
          ^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/python/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1206, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1178, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/layers/heroku_python/dependencies/lib/python3.11/site-packages/django_q/apps.py", line 3, in <module>
    from django_q.conf import Conf
  File "/layers/heroku_python/dependencies/lib/python3.11/site-packages/django_q/conf.py", line 8, in <module>
    import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'

This removal seems premature given that major projects in the Python ecosystem assume its presence.

Metadata

Metadata

Assignees

No one assigned

    Labels

    upstreamIssues in upstream componentsIssues in upstream components

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.