© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
option c) seems less than ideal.
option b) only postpones the problem; we will eventually drop python2, so at some point curtin will need to bridge the gap between python2 and python3 in the set of releases it supports.
option a) is IMHO the best.
There's a clever hack you can use to make a script both valid shell and valid python, to handle the re-execing as whichever version of python is correct. Maybe this is useful to you?
https:/