Hi Dima, On 3 Mrz., 11:27, Dima Pasechnik <[email protected]> wrote: > Hi Simon, > I reported this on sage-release already, and Jeroen is taking care of > it.
I see #11754, but this is only taking care of the README and __init__.py file in this particular case. But what about my second point? I suggest to add a new method sage.misc.hg.HG.local_changes(). It is supposed to return names of all modified tracked files, and of all new untracked files that are either .py or .pyx (if I am not mistaken, .c and .cpp and .h files can appear during compilation, I had a "core" file in devel/sage, ..., that's why I suggest the restriction to new .py and .pyx files). That new method should then have a doc test sage: hg_extcode.local_changes() [] sage: hg_root.local_changes() [] sage: hg_sage.local_changes() [] sage: hg_sagenb.local_changes() [] sage: hg_scripts.local_changes() [] Do you think this would be a good idea? Cheers, Simon -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
