Obviously people are welcome to talk about Sage code here. Please do continue to post: do not take Dima's response as any discouragement to post about Sage code.
On Monday, September 29, 2025 at 8:02:15 AM UTC-7 [email protected] wrote: > On Mon, Sep 29, 2025 at 9:49 AM Georgi Guninski <[email protected]> wrote: > > > > > 4. Historically (at least in my experience) Sage developers were > careful to maintain backwards compatibility, > > > > I think a major backwards compatibility is the order of keyword > > arguments with default values. > > Several year ago I had to do mass replacements in my code. > > > > I needed Graph.edges(labels=False) and I did `G.edges(False)`. > > Sage release made the first argument of .edges `vertices` instead of > > `labels` and my code failed. > > The whole thread is about backwards compatibility for the build system > and related development information - ways the relevant content is > delivered (sic!). > Build systems evolve, development platforms evolve, websites evolve. > We obviously don't offer compatibility with Mercurial VCS and trac > patchquilts > we used to use. > Nobody talks about Sage code here (except perhaps setup.py - which > went out of Python fashion years ago) > > > > > -- > > 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 [email protected]. > > To view this discussion visit > https://groups.google.com/d/msgid/sage-devel/CAGUWgD9iUXKDERnpL9z%2BsYrp%2B1tWNV7%2B%3D5BcVOHwAkqbaptuCw%40mail.gmail.com > . > -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/d81497c8-302b-4e13-986e-610cd2e81290n%40googlegroups.com.
