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 at the moment, that's minor.
It looks to me that
hybrid > copy files > pseudo package
On Tuesday, August 23, 2022 at 5:56:01 PM UTC-7 Kwankyu Lee wrote:
> hybrid
>
> Hearty thanks for setting up the vote.
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and
That's https://trac.sagemath.org/ticket/34201
On Tuesday, August 23, 2022 at 6:33:09 PM UTC-7 Nils Bruin wrote:
> It looks like the "lint" CI test needs to have some warnings about
> importing from namespace packages silenced:
>
>
>
It looks like the "lint" CI test needs to have some warnings about
importing from namespace packages silenced:
https://github.com/sagemath/sagetrac-mirror/runs/7983534732?check_suite_focus=true
the output from the relint job is now useless.
--
You received this message because you are
On Wednesday, August 24, 2022 at 9:18:06 AM UTC+9 Travis Scrimshaw wrote:
> Éric, what do you think about adding such things to SageManifolds? Could
> this be feasible?
>
It is embarrassing that an idea of attaching ".length()" method to a line
segment graphics object leads to SageManifolds.
Try the checkbox "Show property changes" on the ticket?
On Tuesday, August 23, 2022 at 6:02:53 PM UTC-7 Travis Scrimshaw wrote:
> I think this is something that has to do with more recent versions of
> Firefox, as I can see everything in Chrome, but I only see the changes to
> the ticket that
I think this is something that has to do with more recent versions of
Firefox, as I can see everything in Chrome, but I only see the changes to
the ticket that have comments. So if someone, say, changes only the branch
field or the milestone, I do not see these. Is there something that can be
hybrid
Hearty thanks for setting up the vote.
--
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
On Tuesday, August 23, 2022 at 5:47:04 PM UTC-7 François Bissey wrote:
> In the interest of clarity and ease of counting for me, can we keep the
> thread onto votes and possibly voting issues.
>
> Arguments should go back to the ticket or a separate thread please.
>
+1
--
You received this
In the interest of clarity and ease of counting for me, can we keep the
thread onto votes and possibly voting issues.
Arguments should go back to the ticket or a separate thread please.
François
On 24/08/22 12:43, Matthias Koeppe wrote:
On Tuesday, August 23, 2022 at 5:34:01 PM UTC-7 Travis
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
Sage git tree". I recommend to read the discussion on the
If you want to help with the build system of the Sage library,
https://trac.sagemath.org/ticket/34209 is a starting point.
In short, our editable install uses the "setup.py develop" approach, which
is being replaced by PEP 660 editable wheels.
This is a very new feature in setuptools, and so
hybrid > sage psuedo > copy files package
I think we should be mindful that there can be people who build from source
who are not developers. So not having a dependency on git is a small bonus,
but I think almost everyone who has a non-Windows machine has git installed
on their computer by
Can I give my (proxy) vote to Dima?
On Tue, Aug 23, 2022 at 7:38 PM 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 removing the
>
Could it be easily possible to get something inbetween? I like having the
.c files there next to the file (although I have to retrain myself a bit
with typing) rather than having to hunt for them in some obscure
not-well-documented directory. However, I would like that when I make
changes to
In general, I think we are best leaving the drawing classes to just drawing
as a separations-of-concerns. It sounds like we need better integration
between our algebraic objects/implementations and the drawing/plotting
tools. This might include more plot_* functions or specialized
Thanks for sending out the poll, Francois.
I endorse the "hybrid" variant.
On Tuesday, August 23, 2022 at 4:38:40 PM UTC-7 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
I thought it produced wrong results when it was for some composition?
Perhaps I am mistaken or that was some older version of the code. If the
logic is valid for any composition, then we can change the doc.
Best,
Travis
On Monday, August 22, 2022 at 7:59:22 PM UTC+9 axio...@yahoo.de wrote:
>
copy files > hybrid > sage pseudo package
Thanks, François.
Guillermo
On Wed, 24 Aug 2022 at 01: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
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 removing the
current need for gettext and replacing it with gnulib (
https://www.gnu.org/software/gnulib). gnulib is not a
That's probably due to
https://trac.sagemath.org/ticket/32406 'Make "./configure
--enable-editable" the default'
among other things, sys.path now has '$SAGE_ROOT/src' in it. That explains
why the "so" files are there, and the .c files are probably a consequence
of how cython compiles under
https://trac.sagemath.org/wiki/ReleaseTours/sage-9.7#Editableinstallationisnowthedefault
On Tuesday, August 23, 2022 at 10:43:53 AM UTC-7 Thierry
(sage-googlesucks@xxx) wrote:
> Hi,
>
> i recently found that the src/sage directory was cluttered with some .c
> and some .so files, and that the
Thank you, that helped. The files are created when doctesting
src/sage/doctest/forker.py. I've opened
https://trac.sagemath.org/ticket/34416.
On Tuesday, August 23, 2022 at 2:41:39 AM UTC-7 john.c...@gmail.com wrote:
> Whenever a pexpect interface is created, there's an optional parameter to
That's the new default, if you don't want it, pass
"--disable-editable" to ./configure
An advantage of default is that if you only edit Python files, you
don't need to run ./sage -b to update.
(./sage -b creates .pyc files in a separate directory).
I don't recall which of dependency tickets
Hi,
i recently found that the src/sage directory was cluttered with some .c
and some .so files, and that the build artifacts were back in the src/
directory. What is the rationale behind this move ?
Ciao,
Thierry
--
You received this message because you are subscribed to the Google Groups
On Tue, Aug 23, 2022 at 5:31 PM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> Note that this looks like a network failure... but this is happening
> inside the jupyter_jsmol build which tries to install some javascript
> via npm. I thought that the package tarballs were supposed to
On Tue, Aug 23, 2022 at 4:02 PM enriqu...@gmail.com
wrote:
> Actually, now I was able to push my commit even if ssh still gives an error
>
It might be that it gives errors on some keys, and on one of them it works.
>
> El martes, 23 de agosto de 2022 a las 16:44:41 UTC+2, enriqu...@gmail.com
Note that this looks like a network failure... but this is happening
inside the jupyter_jsmol build which tries to install some javascript
via npm. I thought that the package tarballs were supposed to contain
everything to build by themselves.
On Tue, 23 Aug 2022 at 18:27, Vincent Delecroix
Actually, now I was able to push my commit even if ssh still gives an error
El martes, 23 de agosto de 2022 a las 16:44:41 UTC+2, enriqu...@gmail.com
escribió:
> My .ssh folder looks as yours but the ssh command ends with Permission
> denied (publickey).and I cannot push a commit to a ticket.
My .ssh folder looks as yours but the ssh command ends with Permission
denied (publickey).and I cannot push a commit to a ticket. I am in Fedora
36 if it gives a hint.
El viernes, 5 de agosto de 2022 a las 21:40:26 UTC+2, dim...@gmail.com
escribió:
> Another common pitfall are permissions on
Whenever a pexpect interface is created, there's an optional parameter to
say whether or not to make a log file. The default should always be not to
do so. So we should look to see which ones may have the opposite default.
It may be something left over from a debugging session which got committed
On Monday, August 22, 2022 at 12:04:57 PM UTC+9 Travis Scrimshaw wrote:
> I am not sure how much I support that because there is no metric.
>
It is of course euclidean, as you say
> you can do
>
> sage: l = line3d([(1,2,3), (4,5,6)])
> sage: V = RR^3
> sage: (V(l.points[1]) -
32 matches
Mail list logo
