On Fri, Jul 19, 2013 at 11:58:35AM -0400, John.Florian@xxxxxxxx wrote: > > From: tmraz@xxxxxxxxxx > > > > On Fri, 2013-07-19 at 11:24 -0400, John.Florian@xxxxxxxx wrote: > > > > > > > > > Excellent point! If I were caught unaware, I'd much rather have to fix up > > > a bunch shebang lines and learn that I need to get going on my migration > > > pronto than the alternative of finding one day that python2 is just gone > > > where one is left with either a hurried port or downloading python2 from > > > external sources. > > > > The heads-up can be done before the python2 dropping by > > removing /usr/bin/python from python2 package. > > Ah, true indeed. However, I still like the idea of being explicit. If you > want py2, say so in the shebang line. Likewise with py3. How can we get the > very blunt "head's up" and be explicit too? I have no idea when py2 will truly > go away, but I'm convinced it will eventually and I'd like to create my works > in the best possible fashion. Thus far I've relied on the implicit py->py2 and > explicit py3 invocations as that's the way I've seen Fedora set examples, but I > think this should really be more detailed in the packaging guidelines. > I'm not sure if this is a good idea (or in what time frame it may be a good idea. It's definitely too early now and likely too early for F22) but -- if you want something explicit, we could replace /usr/bin/python with something that prints out an error message to switch shebang lines to use /usr/bin/python2 and exits. (Perhaps a warning message to switch shebang lines could be done now, though). -Toshio
Attachment:
pgp5C7JHhH8Nf.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
