[Bug 1831306] Re: squid-deb-proxy is a python2 script

[Rolf Leggewie]

** Description changed:

  [ IMPACT ]
  
  squid-deb-proxy is a python2 script.  I suggest to change the shebang to
  /usr/bin/python2 to reflect this.  The script crashes for users who have
  made python3 the default in bionic.  Anyone with python as python2 is
- fine (the default), but somehow who likes to stay in LTS yet program in
- python3 this results in avoidable and easily fixable problem.
+ fine (the default), but someone who likes to stay in bionic LTS yet
+ program in python3 this results in an avoidable and easily fixable
+ problem.
  
  [ TEST CASE ]
  
  Compare "python2 /usr/share/squid-deb-proxy-client/apt-avahi-discover"
  vs. "python3 /usr/share/squid-deb-proxy-client/apt-avahi-discover".
  
  [ REGRESSION POTENTIAL ]
  
  There should not be any.  It just makes the implicit assumption that the
  script runs via python2 explicit.
  
  The only time there could potentially be an issue is if python2 has been
  explicitly removed AND python pointed to python3.  I have a hard time
  thinking why somebody would do that and such a setup would certainly
  break in a number of other situations.

** Description changed:

  [ IMPACT ]
  
  squid-deb-proxy is a python2 script.  I suggest to change the shebang to
  /usr/bin/python2 to reflect this.  The script crashes for users who have
  made python3 the default in bionic.  Anyone with python as python2 is
  fine (the default), but someone who likes to stay in bionic LTS yet
  program in python3 this results in an avoidable and easily fixable
  problem.
  
  [ TEST CASE ]
  
  Compare "python2 /usr/share/squid-deb-proxy-client/apt-avahi-discover"
  vs. "python3 /usr/share/squid-deb-proxy-client/apt-avahi-discover".
  
  [ REGRESSION POTENTIAL ]
  
- There should not be any.  It just makes the implicit assumption that the
- script runs via python2 explicit.
+ There should not be (m)any.  It just makes the implicit assumption that
+ the script runs via python2 explicit.
  
  The only time there could potentially be an issue is if python2 has been
  explicitly removed AND python pointed to python3.  I have a hard time
  thinking why somebody would do that and such a setup would certainly
  break in a number of other situations.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1831306

Title:
  squid-deb-proxy is a python2 script

Status in squid-deb-proxy package in Ubuntu:
  Fix Released
Status in squid-deb-proxy source package in Bionic:
  New

Bug description:
  [ IMPACT ]

  squid-deb-proxy is a python2 script.  I suggest to change the shebang
  to /usr/bin/python2 to reflect this.  The script crashes for users who
  have made python3 the default in bionic.  Anyone with python as
  python2 is fine (the default), but someone who likes to stay in bionic
  LTS yet program in python3 this results in an avoidable and easily
  fixable problem.

  [ TEST CASE ]

  Compare "python2 /usr/share/squid-deb-proxy-client/apt-avahi-discover"
  vs. "python3 /usr/share/squid-deb-proxy-client/apt-avahi-discover".

  [ REGRESSION POTENTIAL ]

  There should not be (m)any.  It just makes the implicit assumption
  that the script runs via python2 explicit.

  The only time there could potentially be an issue is if python2 has
  been explicitly removed AND python pointed to python3.  I have a hard
  time thinking why somebody would do that and such a setup would
  certainly break in a number of other situations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1831306/+subscriptions