[sage-devel] feedback on construction functor for symmetric functions

At https://github.com/sagemath/sage/pull/37220, I implemented a (simple minded) construction functor for symmetric functions. The only major user visible change should be that sage: sZ = SymmetricFunctions(ZZ).s() sage: sQ = SymmetricFunctions(QQ).s() sage: sZ[1,1] + sQ[2] s[1,1] + s[2] now wor

Re: [sage-devel] Proposal: Make pytest, pytest_xdist, pytest_mock, python_build standard packages

I believe I'm the person who introduced that long standing policy. It was indeed motivated by a significant paying customer's requirement to install Sage entirely from source, and without an external network. I believe no such customers have supported the Sage project for about a decade, so I

Re: [sage-devel] Proposal: Make pytest, pytest_xdist, pytest_mock, python_build standard packages

5 On 11 February 2024 13:21:46 GMT, kcrisman wrote: > > >I believe I'm the person who introduced that long standing policy. It >was indeed motivated by a significant paying customer's requirement >to install Sage entirely from source, and without an external network. >I believe no such custo

Re: [sage-devel] Proposal: Make pytest, pytest_xdist, pytest_mock, python_build standard packages

How about we initiate a vote on letting standard packages be pip packages? The vote should be rather on assuming internet connectivity for sage build than on allowing standard pip packages. They are equivalent conditions. Right? -- You received this message because you are subscribed to the

[sage-devel] Re: Google Summer of Code: Organization application deadline Feb 6!

So, if i understand what you mean correctly, 1) would go along making it easier from the sage part to implement tactics like polyrith (which right now calls the sagecell server to prove equalities between expressions using groebner basis)? That sounds very nice. In particular I would like to n

Re: [sage-devel] Proposal: Make pytest, pytest_xdist, pytest_mock, python_build standard packages

Maybe you can get the best of both worlds? I mean: use those packages as pip packages, but also have a way to download a big tarball with those packages, and then pip-install them from that local copy? El domingo, 11 de febrero de 2024 a las 15:50:17 UTC+1, Kwankyu Lee escribió: > How about we

[sage-devel] Re: feedback on construction functor for symmetric functions

Apart from that, I think the last bit I need to do is to make the TensorProductFunctor inherit from MultivariateConstructionFunctor, to make coercion work for things like sage: h = SymmetricFunctions(ZZ).h() sage: T = tensor([h, h]) sage: T.base_ring() Integer Ring sage: 1/2*T.an_element() (whi

[sage-devel] Re: Google Summer of Code: Organization application deadline Feb 6!

On Sunday, February 11, 2024 at 7:10:59 AM UTC-8 mmarco wrote: if i understand what you mean correctly, 1) would go along making it easier from the sage part to implement tactics like polyrith (which right now calls the sagecell server to prove equalities between expressions using groebner basi

Re: [sage-devel] Proposal: Make pytest, pytest_xdist, pytest_mock, python_build standard packages

On 11 February 2024 15:34:18 GMT, mmarco wrote: >Maybe you can get the best of both worlds? I mean: use those packages as >pip packages, but also have a way to download a big tarball with those >packages, and then pip-install them from that local copy? > >El domingo, 11 de febrero de 2024 a l

Re: [sage-devel] Proposal: Make pytest, pytest_xdist, pytest_mock, python_build standard packages

Reminder to all to please keep the thread on topic (= vote on making these packages standard). Focus matters! On Sunday, February 11, 2024 at 6:21:44 AM UTC-8 Dima Pasechnik wrote: Sage 10.2 tarball is 1.3Gb, of which upstream/ subdirectory takes 80%. (for some reason there's also .git/ - some

[sage-devel] [Proposal] allow standard packages to be pip packages, reduce source tarball size

Currently the standard packages cannot be pip packages, i.e. we must, in effect, vendor them. This entails an extra effort which is often not needed, in particular as we patch only very few Python packages. Pip packages are on the other hand installed straight from PyPI. Good examples of standa

[sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

I think it's a bit too quick to already call a vote. I would suggest that you take the time to collect and link previous discussions on this topic, so that participants can review the known arguments, viewpoints, and requirements. Example (from my previous post): https://groups.google.com/g/sa

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

On 11 February 2024 19:50:17 GMT, Matthias Koeppe wrote: >I think it's a bit too quick to already call a vote. I would suggest that >you take the time to collect and link previous discussions on this topic, >so that participants can review the known arguments, viewpoints, and >requirements.

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

On Sunday, February 11, 2024 at 12:26:41 PM UTC-8 Dima Pasechnik wrote: On 11 February 2024 19:50:17 GMT, Matthias Koeppe wrote: >I think it's a bit too quick to already call a vote. I would suggest that >you take the time to collect and link previous discussions on this topic, >so that part

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

As I mentioned in the thread that motivated this one, it would be relevant to stablish if it is possible to move those packages from standard to pip, while still having a way to install sage without an internet connection. If the effort is not too much, I think it would make sense to provide tha

[sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

I'll provide some context and pointers that readers may find helpful to participate in the discussion and vote. - terminology: https://deploy-livedoc--sagemath.netlify.app/html/en/developer/packaging#package-types - tooling: https://deploy-livedoc--sagemath.netlify.app/html/en/developer/packagin

[sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

On Sunday, February 11, 2024 at 1:46:40 PM UTC-8 Matthias Koeppe wrote: I'll make an attempt to quantify this cost Here's an illustration of the workflow for making python_build a standard "wheel" package, as proposed in https://groups.google.com/g/sage-devel/c/MIU-xo9b7pc: *$ git checkout -

[sage-devel] Re: Google Summer of Code: Organization application deadline Feb 6!

Miguel, can you add the project to the wiki page (or tell me the information here), even if it is not fully prepared? It will help increase our chances of being selected for GSoC again. For everyone, there is a new 90 hour option for GSoC project lengths this year. Best, Travis On Monday, Feb

[sage-devel] Re: morphisms between multivariate polynomial rings

Hi Martin, That is coming from this: sage: type(m) Although I don't think we have a specific "all morphisms should inherit from this ABC (or generic base class)" specification. It might be easy to get something to work for it. Are you thinking of the difficulty of determining a consistent

[sage-devel] Re: feedback on construction functor for symmetric functions

Hi Martin, I plan to look closely at this this week. Unfortunately I cannot offer anything quick now. Best, Travis On Monday, February 12, 2024 at 2:42:52 AM UTC+9 Martin R wrote: > Apart from that, I think the last bit I need to do is to make the > TensorProductFunctor inherit from Multiv

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

On 11 February 2024 21:46:40 GMT, Matthias Koeppe wrote: >I'll provide some context and pointers that readers may find helpful to >participate in the discussion and vote. >- terminology: >https://deploy-livedoc--sagemath.netlify.app/html/en/developer/packaging#package-types >- tooling: >htt

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

On 11 February 2024 22:47:24 GMT, Matthias Koeppe wrote: >On Sunday, February 11, 2024 at 1:46:40 PM UTC-8 Matthias Koeppe wrote: > >I'll make an attempt to quantify this cost > > >Here's an illustration of the workflow for making python_build a standard >"wheel" package, as proposed in >htt

Re: [sage-devel] Re: [Proposal] allow standard packages to be pip packages, reduce source tarball size

On Sunday, February 11, 2024 at 3:34:46 PM UTC-8 Dima Pasechnik wrote: On 11 February 2024 22:47:24 GMT, Matthias Koeppe wrote: >On Sunday, February 11, 2024 at 1:46:40 PM UTC-8 Matthias Koeppe wrote: > >I'll make an attempt to quantify this cost > >Here's an illustration of the workflow fo

[sage-devel] add transformation matrix interface for BKZ

Hi. sage-devel members. I am kiona. I want to contribute devel for some math/crypto packages. [background] I created Coppersmith small root method packages: kionactf/coppersmith(github.com) I am considering the package would be included in Sagemath tree.

Re: [sage-devel] add transformation matrix interface for BKZ

Regarding fplll and flatter, Sage already has an interface with fplll (via fpylll), and issue #37207 is adding an interface call to flatter (the new pari implementation). On 11/02/2024 23:48, user ctf wrote: Hi. sage-devel members. I am kiona. I want to contribute devel for some math/crypto pa

[sage-devel] Re: Problem extracting base B fractional digits of a number

On Sat, Feb 10, 2024 at 6:24 PM Georgi Guninski wrote: > > > ``` > def base_B_digits(A, B,prot=False): > digits=[] > fractional_part = A - int(A) > while fractional_part != 0: >digit = int(fractional_part * B) >digits.append(digit) >fractional_part = fractional_

Re: [sage-devel] Re: Problem extracting base B fractional digits of a number

Yes, because 1 / 2 is mathematically infinite in base 3, just like how A=1/3 and B=10 doesn't terminate. On 12/02/2024 07:31, Georgi Guninski wrote: On Sat, Feb 10, 2024 at 6:24 PM Georgi Guninski wrote: ``` def base_B_digits(A, B,prot=False): digits=[] fractional_part = A - int(A)

Re: [sage-devel] Re: Problem extracting base B fractional digits of a number

On Mon, Feb 12, 2024 at 9:35 AM Gareth Ma wrote: > > Yes, because 1 / 2 is mathematically infinite in base 3, just like how A=1/3 > and B=10 doesn't terminate. > Indeed, it is periodic and infinite. When I use code finite precision I expect it to terminate. It works with python `float` too. btw,