Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use an available python2 binary name in debian templates. #203

Merged
merged 2 commits into from
Jul 12, 2024
Merged

Use an available python2 binary name in debian templates. #203

merged 2 commits into from
Jul 12, 2024

Commits on Jul 10, 2024

  1. Check path for python2 binary name when generating deb info. 

    Ubuntu Focal and Jammy install python2 with python-all-dev.
Rather than requiring that tests and downstream packages always install
python-is-python2 (seemingly unavailable on jammy), check the current
path for each binary and use the first one found, preferring `python`
when it is available to maintain current behavior but using `python2` if
it's the only option.

This unblocks testing python2 package generation with python3-stdeb in
test-2and3.sh.
    @nuclearsandwich
    nuclearsandwich committed Jul 10, 2024
    Configuration menu
    Copy the full SHA
    abb982c View commit details
    Browse the repository at this point in the history

  2. Add a test for python2 package generation from python3. 

    Although I am planning to drop support for installing/running stdeb from
python2 I am hoping to preserve, at least for a while, support for
generating python2 packages.

Howveer, this case doesn't appear to be tested so I've added an
additional case when testing python3.
    @nuclearsandwich
    nuclearsandwich committed Jul 10, 2024
    Configuration menu
    Copy the full SHA
    0eecfbd View commit details
    Browse the repository at this point in the history