> cp: cannot access *.sage In short: that does not seem to be a new problem.
I've seen this line before (I think I get it every time I build a bdist on my Macs), and I admit, that I never cared. The files ending in *.sage are supposed to be loadable/attachable scripts (in)to Sage sessions, see e.g. the examples spkg/subdir, but the copy command for them while creating a bdist is most probably a historical leftover, and not needed. It should be easy to remove. If you wish so, open a (another?!?) ticket and put me in Cc. Or add a "cleaned up" version to trac #7407. Cheers, Georg -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
