On Mon, Feb 12, 2024 at 10:01 PM Matthias Koeppe <matthiaskoe...@gmail.com> wrote: > > On Monday, February 12, 2024 at 10:49:04 AM UTC-8 Dima Pasechnik wrote: > > requirements.txt might as well specify the range, and this is used too e.g. > > build/pkgs/phitigra/requirements.txt has > phitigra>=0.2.6 > > > Yes, as I said in > https://groups.google.com/g/sage-devel/c/5kmxaw105lg/m/9rF77fvFAAAJ, ""Pip" > packages can either be pinned to a specific version, or set acceptable > version ranges, or be entirely unconstrained. This is set in the file > requirements.txt in the package directory." > > So this is all [...] confusing > > > That's why I'm taking the time to explain it clearly for the benefit of > everyone.
I am sorry: I claimed that Sage has about 5 different ways to specify/restrict versions of its packages, and this makes it hugely confusing. You disagreed, but now you say that it needs an explanation. What really needs an explanation is how we ever went this far on a garden path. :-) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq2CVh1bbe2EishyAkGUtn%3DEMgcOyonoLUTG2sAYSXZwtQ%40mail.gmail.com.
