Well thats because we write utility scripts as standalone files. Instead of implementing the business logic in a library with test coverage.
On Sunday, May 29, 2016 at 12:11:06 PM UTC+2, Johan S. R. Nielsen wrote: > > This is probably not related to exactly this release, but I have the > following small compilation problem: > > On Arch linux, "python" by default Python 3, while python2 is Python 2. > This causes a build error in the sage-uncompress-spkg script, for > instance: > > $ make > <snip> > [install] [patch-2.7.5] Setting up build directory for patch-2.7.5 > [install] [patch-2.7.5] File > "/home/jsrn/mat/sage_coding_project/build/bin/sage-uncompress-spkg", line > 35 > [install] [patch-2.7.5] self.umask = os.umask(0777) > [install] [patch-2.7.5] ^ > [install] [patch-2.7.5] SyntaxError: invalid token > <snip> > > The issue is sidestepped by editing sage-uncompress-spkg to explicitly > run python2. Is there a more robust way? And why isn't > sage-uncompress-spkg Python3-ready? > > Best, > Johan > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
