Currently, some code is unable to be included in Sage (except as an optional package) because it is not 32-bit safe. One example close to my heart is Drew Sutherland's smalljac package for computing L-series of hyperelliptic curves; Drew's position is that "life is too short to worry about overflowing a 32-bit integer."
I was reminded of this by Apple's announcement that iOS 11 will drop support for 32-bit apps. I agree with the position that now is not the time for Sage to follow suit; however, it would be helpful if some 64-bit-only code could be included in Sage's doctesting framework. Is it feasible now, or could it be in the near future, for some code to be configured so that it raises a NotImplementedError in a 32-bit environment, and is only doctested in a 64-bit environment? I guess this is related to the ongoing discussions about package management. Right now, it is not so great to have something be relegated to a manual install just because it is 64-bit-only. But if the package management system could identify certain packages as being "64-bit-only but otherwise mandatory", then the installer could take care of including them whenever it detects a 64-bit platform. (And of course binaries could be distributed accordingly.) Kiran -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
