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

python setup_helper ignores --install-base flag

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

@christophfroehlich is already working on this.

Since Apr 17, 2026.

  • #348 by @christophfroehlich — open
  • #393 by @MarqRazz — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
build-system

Research direction

Start by reading setup_helper.generate_parameter_module and how it handles --build-base; reproduce the issue with the colcon build --merge-install --install-base=/opt/alt-install-path-v0 command from the report. Done means the generated Python parameter module is placed under the selected install base rather than the workspace's default install/ path. A linked open pull request means this work may already be underway.

Written by the indexing model from the issue text.

Description

While setup_helper.generate_parameter_module parses args and respects --build-base, it assumes the default 'install' path and ignores the --install-base argument.

For example:

colcon build --merge-install --install-base=/opt/alt-install-path-v0

Results in the ROS python package being installed to:

/opt/alt-install-path-v0/lib/python3.10/site-packages/foo/...

But the generated code gets left behind all by itself in the workspace

$ tree install/
install/
└── foo
    └── lib
        └── python3.10
            └── site-packages
                └── foo
                    ├── foo_parameters.py

I believe this is different but related to the churn and discussion of similar issues in #207 #236 #237

Dominant language
Python
Stars
385
Forks
81
PR merge metrics
No merged PRs in 30d

Getting set up

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 PickNikRobotics/generate_parameter_library

All issues in PickNikRobotics/generate_parameter_library

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.