I don't consider this approved, as my complaint about the previous discussions
and related proposals and credits due is not addressed, and the technical
discussion on how we implement this is not finished.
Dima
On 19 August 2024 19:16:54 BST, Matthias Koeppe
wrote:
>On Sunday, August 4, 20
On Tuesday, August 20, 2024 at 8:22:35 PM UTC-5 Kwankyu Lee wrote:
it is not a bad idea for a non-developer user to install sage from source.
I disagree. It *is* a bad idea, for so many reasons:
* It requires a lot of time and work which is completely unrelated to using
Sage.
* It will almos
On Wednesday 21 August 2024 at 08:03:03 UTC-7 marc@gmail.com wrote:
On Tuesday, August 20, 2024 at 8:22:35 PM UTC-5 Kwankyu Lee wrote:
it is not a bad idea for a non-developer user to install sage from source.
I disagree. It *is* a bad idea, for so many reasons:
* It requires a lot of tim
Hello,
something bad seems to happen when touching pyx files. Sage build ok but
fails to start, unless I recompile with "make sagelib-clean & make build"
I got the following message at startup, see below. Any idea about the issue
?
Frédéric
Traceback (most recent call last):
File "/home/cha
On Wednesday 21 August 2024 at 09:09:22 UTC-7 Frédéric Chapoton wrote:
TypeError: C function sage.misc.randstate.current_randstate has wrong
signature (expected struct __pyx_obj_4sage_4misc_9randstate_randstate *(int
__pyx_skip_dispatch), got struct __pyx_obj_9randstate_randstate *(int
__pyx_s
Using cython within Sage via the %%cython magic command definitely does*
not *require building Sage from source. That magic command works fine in
the Sage_macOS binary distribution of SageMath. The cython pip package is
included in that binary distribution, because it gets built and installed
I should add that, in truth, "xcode-select --install" is all that is really
required in order to build Sage. But you would not get that impression
from reading about how to build Sage. (I consider that to be a great
strength of Sage's current structure, and I am also aware that many people
s
On 21 August 2024 16:03:02 BST, Marc Culler wrote:
>
>On Tuesday, August 20, 2024 at 8:22:35 PM UTC-5 Kwankyu Lee wrote:
>
> it is not a bad idea for a non-developer user to install sage from source.
>
>
>I disagree. It *is* a bad idea, for so many reasons:
it's only if you are on a bad platf
On 21 August 2024 17:09:22 BST, "Frédéric Chapoton"
wrote:
>Hello,
>
>something bad seems to happen when touching pyx files. Sage build ok but
>fails to start, unless I recompile with "make sagelib-clean & make build"
"make build"
alone does not work?
>
>I got the following message at st
Since Tobias Diez's PR https://github.com/sagemath/sage/pull/36982 ("Make
pyproject.toml the source for build dependencies"; TW: PR comments), merged
in Sage 10.4, the version constraints of the packages that happen to be
build dependencies of the Sage library (enumerated in
https://github.com/
On Wednesday, August 21, 2024 at 6:03:29 PM UTC+1 Marc Culler wrote:
Using cython within Sage via the %%cython magic command definitely does*
not *require building Sage from source. That magic command works fine in
the Sage_macOS binary distribution of SageMath. The cython pip package is
in
On Wednesday, August 21, 2024 at 9:15:36 AM UTC-7 Nils Bruin wrote:
On Wednesday 21 August 2024 at 09:09:22 UTC-7 Frédéric Chapoton wrote:
TypeError: C function sage.misc.randstate.current_randstate has wrong
signature (expected struct __pyx_obj_4sage_4misc_9randstate_randstate *(int
__pyx_ski
so you mean this is caused by me playing with "cython -3 -a", right ?
How can I force the correct re-build now ?
Le mercredi 21 août 2024 à 19:50:20 UTC+2, Matthias Koeppe a écrit :
> On Wednesday, August 21, 2024 at 9:15:36 AM UTC-7 Nils Bruin wrote:
>
> On Wednesday 21 August 2024 at 09:09:22
On Wed, Aug 21, 2024 at 12:35 PM Dima Pasechnik wrote:
> what if you have a version mismatch between the toolchain used to build
> the shipped binary,
> and XCode you installed locally? I'd expect trouble, in particular with
> C++.
>
When I tested the %%cython magic command I was running a beta
It appears to me that we are seeing a culture clash here. I think what
Marc says is correct in regard to mac users, but, for all I know, it may be
less (or not at all) true about linux users.
In particular, I am pretty sure that the vast majority of mac users have
never built a program from so
I think the clash is much more basic than that.
It is developers versus users. Users who hoped to do (some) mathematics
with a computer.
So far, it seems to me most discussions are developer-centric, Marc being
among the exceptions giving another POV.
Guillermo
On Wed, 21 Aug 2024 at 21:15, dm
On Wednesday 21 August 2024 at 12:36:02 UTC-7 GMS wrote:
I think the clash is much more basic than that.
It is developers versus users. Users who hoped to do (some) mathematics
with a computer.
So far, it seems to me most discussions are developer-centric, Marc being
among the exceptions giv
In the interest of keeping the discussion focused, I would ask that
commenters use a separate thread if they wish to comment on the matters of
"building the Sage distribution from source vs. using a prebuilt binary
distribution" and other unrelated matters. Thanks.
--
You received this message
Yes. "make sagelib-clean" fixes it.
On Wednesday, August 21, 2024 at 11:00:51 AM UTC-7 Frédéric Chapoton wrote:
> so you mean this is caused by me playing with "cython -3 -a", right ?
>
> How can I force the correct re-build now ?
>
> Le mercredi 21 août 2024 à 19:50:20 UTC+2, Matthias Koeppe a é
On Wednesday, August 21, 2024 at 7:33:26 AM UTC-7 Dima Pasechnik wrote:
I don't consider this approved, as my complaint about the previous
discussions and related proposals and credits due is not addressed
I'll note that extraordinary claims such as those that Dima Pasechnik made
above in
htt
On Wednesday 21 August 2024 at 13:16:48 UTC-7 Matthias Koeppe wrote:
On Wednesday, August 21, 2024 at 7:33:26 AM UTC-7 Dima Pasechnik wrote:
I don't consider this approved, as my complaint about the previous
discussions and related proposals and credits due is not addressed
I'll note that extr
I am sorry.
Once I tried to start a discussion on this developers vs. users topic.
Nobody answered. My fault surely.
I shall stop here.
Guillermo
On Wed, 21 Aug 2024 at 22:16, Matthias Koeppe
wrote:
> In the interest of keeping the discussion focused, I would ask that
> commenters use a sepa
On 21 August 2024 18:12:55 BST, Matthias Koeppe
wrote:
>On Wednesday, August 21, 2024 at 7:33:26 AM UTC-7 Dima Pasechnik wrote:
>
>I don't consider this approved, as my complaint about the previous
>discussions and related proposals and credits due is not addressed
>
>
>I'll note that extraor
> the version constraints of the packages that happen to be build
dependencies of the Sage library (enumerated in
https://github.com/sagemath/sage/blob/develop/bootstrap#L36) are set in
https://github.com/sagemath/sage/blob/develop/src/pyproject.toml#L3
Right (adhering to the standard of moder
On Wednesday, August 21, 2024 at 1:48:39 PM UTC-7 Nils Bruin wrote:
On the google groups comment linked to by the second reference you give,
Dima does link to a very explicit proposal that does share substantial
features with the proposed policy change discussed here.
Nils, what are these "sub
On 21 August 2024 22:01:40 BST, Matthias Koeppe
wrote:
>On Wednesday, August 21, 2024 at 1:48:39 PM UTC-7 Nils Bruin wrote:
>
>On the google groups comment linked to by the second reference you give,
>Dima does link to a very explicit proposal that does share substantial
>features with the p
On Tuesday, August 6, 2024 at 6:17:14 PM UTC-7 Dima Pasechnik wrote:
On Tue, Aug 6, 2024 at 9:45 PM Nathan Dunfield
wrote:
> As I understand it, while both proposals result in binary wheels being
pulled off PyPI for certain standard packages, they differ in that:
>
> a) The current proposal
On Tuesday, August 20, 2024 at 6:44:50 PM UTC-7 Matthias Koeppe wrote:
On Tuesday, August 20, 2024 at 5:42:42 PM UTC-7 John H Palmieri wrote:
I just built Sage on an OS X machine with a bunch of homebrew packages
installed. It took under 20 minutes to build everything except the
documentation,
On Wednesday, August 21, 2024 at 2:12:30 PM UTC-7 tobia...@gmx.de wrote:
> the version constraints of the packages that happen to be build
dependencies of the Sage library (enumerated in
https://github.com/sagemath/sage/blob/develop/bootstrap#L36) are set in
https://github.com/sagemath/sage/blo
On Wednesday 21 August 2024 at 15:29:05 UTC-7 Matthias Koeppe wrote:
On Wednesday, August 21, 2024 at 2:12:30 PM UTC-7 tobia...@gmx.de wrote:
> the version constraints of the packages that happen to be build
dependencies of the Sage library (enumerated in
https://github.com/sagemath/sage/blob/d
Bigrading is a very interesting solution. I take it that the differential
should have degree (1,0).
Sorry I forgot to answer that. The differential must have total degree 1
(that is, bidegree (i,j) with i+j = 1). So in your case, just change every
degree i to (i,2).
--
You received this me
> The tighter version constraints are needed by the Sage distribution
Then please specify these version constraints in sage distribution and not
in sage-lib (eg by providing a version_constraint.txt file that is
compatible with the version constraints of sage-lib and the tighter
constraints s
On Wednesday, August 21, 2024 at 4:58:42 PM UTC-7 Kwankyu Lee wrote:
> The tighter version constraints are needed by the Sage distribution
Then please specify these version constraints in sage distribution and not
in sage-lib (eg by providing a version_constraint.txt file that is
compatible wit
33 matches
Mail list logo
