>
> I have no idea what your argument is for the second part. Separations of
> concerns means ...
>
I didn't use the phrase in its precise meaning (so I quoted it)
I meant that you can write pythagorean formula, which is just what you need
to compute the length of a line segment object,
It also happened to me on one of my system (fedora 36).
After removing yarnpkg rpm, it builds ok.
(will post the log later...)
Kazuyoshi
2022年8月25日(木) 1:28 Samuel Lelievre :
> Now tracked at
>
> - Sage Trac ticket #34421
> Fix timeout in jupyter_jsmol installation
>
However, I don't think it should take 30 minutes, that seems far too long
to me to check everything, even on a slow system. The longest part to me
always seems to be checking the documentation part.
Samuel, how long does "make build" take for you?
Best,
Travis
On Thursday, August 25, 2022 at
Yes we do, otherwise it doesn't make sense mathematically. There are lots
of different metrics I can use on 2D vectors that make sense. Otherwise any
(physical paper) maps would be very impractical. I think it is generally
bad practice to assign mathematical significant things to classes that
Ah, I see. That fixed it. Thanks. I never knew about that as I never paid
any attention to that box. it is annoying that changed on a Firefox
update...Oh well.
Best,
Travis
On Wednesday, August 24, 2022 at 10:06:05 AM UTC+9 Matthias Koeppe wrote:
> Try the checkbox "Show property changes" on
> If you want to work on this, could you open at ticket please?
Of course! This is now: https://trac.sagemath.org/ticket/34425
Le mercredi 24 août 2022 à 16:56:07 UTC-4, Matthias Koeppe a écrit :
> It would make sense to configure it in the same way as we do in
> src/tox.ini (see section
It would make sense to configure it in the same way as we do in src/tox.ini
(see section
testenv:pycodestyle-minimal).
https://github.com/sagemath/sage/blob/develop/src/tox.ini#L92
If you want to work on this, could you open at ticket please?
On Wednesday, August 24, 2022 at 1:41:40 PM UTC-7
Our build system does not know the precise dependence of sagelib on its
source files and other components.
To know if it needs to be rebuilt, we just invoke sagelib's build system.
This is akin to https://trac.sagemath.org/ticket/29711
Likewise for the docbuild: It kind of depends on source
On Thursday, August 25, 2022 at 4:06:14 AM UTC+9 Sébastien Labbé wrote:
> Is there already a handy way to get the same result in Sage?
>>
>
>> You can image other useful methods attached to a graphics object.
>>
>
> For 2d lines, it returns a Graphics object which has a length.
>
Right. That
Dear sage-devel,
Having built Sage successfully from source with the command
`make configure && make`, if I then immediately run `make`
a second time in the same shell session, shouldn't that second
run have nothing to build, and thus terminate almost instantly?
Here is an example of building
> Is there already a handy way to get the same result in Sage?
>
> You can image other useful methods attached to a graphics object.
>
For 2d lines, it returns a Graphics object which has a length:
sage: l = line([(1,2),(10,20)])
sage: k = line([(10,20),(100,200)])
sage: len(l)
1
sage:
Now tracked at
- Sage Trac ticket #34421
Fix timeout in jupyter_jsmol installation
https://trac.sagemath.org/ticket/34421
(thanks Dima for opening the ticket).
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
hybrid > copy files > sage pseudo package
Vincent
--
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
My and djoyner votes are for
sage pseudopkg
Dima
On Wed, 24 Aug 2022, 00:38 François Bissey, wrote:
> Hi all,
>
> https://trac.sagemath.org/ticket/34152 needs help to decide what solution
> we implement going forward.
>
> The ticket is concerned with updating the bootstrap process by
On Wed, 24 Aug 2022, 03:49 Nils Bruin, wrote:
> hybrid.
>
> [it provides an immediate solution to an urgent problem *and* it provides
> a reasonably automated path for updating. It does indeed put some files
> under sage git control that shouldn't be, but compared to the urgency of
> the problem
On Wed, 24 Aug 2022, 01:43 Matthias Koeppe,
wrote:
> On Tuesday, August 23, 2022 at 5:34:01 PM UTC-7 Travis Scrimshaw wrote:
>
>> I also fully agree with Dima that gnulib has no business being in Sage's
>> git tree
>>
>
> This is a mischaracterization. None of the approaches puts "gnulib in the
16 matches
Mail list logo
