Absolute path to executable

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Start by locating the get_*_command_line_invocation() methods and inspect how they determine the executable name. Update the command-line invocation output so its first element is the absolute path to the executed script, then run the repository's relevant tests and verify the output distinguishes scripts with the same name in different locations.

Written by the indexing model from the issue text.

Description

Type: Feature

Currently the get_*_command_line_invocation() methods start the command line with the executable, but it's only the name of the script being run. For replicability's sake, this should really be the absolute path to the script executed, otherwise two different users could be running scripts of the same name in different locations and they'd be different scripts, and therefore behave differently, leading to confusing that this package is intended to address.

Dominant language
Python
Stars
48
Forks
6
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 sandialabs/reverse_argparse

All issues in sandialabs/reverse_argparse

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.