Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

should `egg_info` target be supported without library checks?

Open
#80 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
build-system

Research direction

Start by reading setup.py and tracing why setup.py invocations trigger the runtime library check, with attention to the egg_info target. Reproduce the behavior using egg_info, then verify that pipenv-style locking can run it on a platform without the library check.

Written by the indexing model from the issue text.

Description

Currently any invocation of setup.py, except for --version, triggers a runtime library check.

I think it precludes using the egg_info target on other platforms. E.g. pipenv will run this target when doing a lock.

Dominant language
C
Stars
522
Forks
79
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from systemd/python-systemd

All issues in systemd/python-systemd

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.