I'm late to discussion (also sorry for top-posting) but I don't see any
discussion of a middle ground where rather than "switching" starkly to
GitHub, just enabling issues and PRs on GitHub and see how it goes.
We tried the same experiment with GitLab some time ago with synchronizing
to Trac, and
Hello,
(For anyone confused about this question, it's about the Windows
release of Sage).
The command you're trying to run is not going to work. I can see you
probably copied it from the desktop shortcut that launches Sage in a
terminal Window. mintty.exe is the terminal emulator that comes
Hello,
I don't know at what level it should be, I have a notebook here
introducing some *very basic* use of graphs in Sage:
https://github.com/gabayae/sage-days-102/blob/master/intro_to_graph_theory.ipynb
It's less an introduction to graph theory (in a pedagogical sense)
but more an introduction
Hello,
Did you try the "sudo yum install" command mentioned in the output,
especially the first one (the really long one). Copy and paste that to
install as many dependencies as possible from the system.
On Wed, Oct 6, 2021, 22:11 Catherine Ray wrote:
> Dear Developer,
>
> I am attempting to
On Thu, Apr 29, 2021 at 2:30 PM julian...@fsfe.org
wrote:
>
> Hi Dima and Abhishek.
>
> On Thursday, April 29, 2021 at 12:44:33 PM UTC+2 dim...@gmail.com wrote:
>>
>> On Thu, Apr 29, 2021 at 9:37 AM Abhishek cherath wrote:
>>
>> > For some reason the CI build for 9.2 release seems to have
.
>>
>> On Fri, Nov 29, 2019 at 3:51 PM Frédéric Chapoton wrote:
>> >
>> > Hello Erik,
>> >
>> > Would you make a ticket and upload a branch on trac, please ?
>> >
>> > Frederic
>> >
>> > Le jeudi 23 mai
Cool, thanks!
On Mon, Mar 15, 2021 at 8:50 PM Matthias Koeppe
wrote:
>
> The SageMath distribution is now listed on repology.
>
> See https://repology.org/repository/sagemath
> and https://repology.org/projects/?inrepo=sagemath
>
> Many thanks to Dmitry Marakasov, who implemented a parser for
On Wed, Mar 10, 2021 at 1:29 PM E. Madison Bray wrote:
>
> On Tue, Mar 9, 2021 at 6:13 PM Nathan Dunfield wrote:
> >
> > An update: I just tried three different binary versions on Linux: The
> > Ubuntu 20.04 binary posted at SageMath.org, the sagemath/sagemath:d
On Thu, Mar 11, 2021 at 5:18 AM Nathan Dunfield wrote:
>
>
>
> On Wednesday, March 10, 2021 at 4:50:41 AM UTC-6 Dima wrote:
>>
>> numpy does this:
>> https://numpy.org/devdocs/docs/howto_build_docs.html
>>
>> you can only build numpy docs after numpy is installed.
>
>
> Of course, with numpy
On Thu, Mar 11, 2021 at 1:20 PM E. Madison Bray wrote:
>
> On Thu, Mar 11, 2021 at 12:52 PM Dima Pasechnik wrote:
> >
> > On Thu, Mar 11, 2021 at 10:11 AM Dima Pasechnik wrote:
> > >
> > > On Wed, Mar 10, 2021 at 4:00 PM E. Madison Bray
> > > wrot
On Thu, Mar 11, 2021 at 12:52 PM Dima Pasechnik wrote:
>
> On Thu, Mar 11, 2021 at 10:11 AM Dima Pasechnik wrote:
> >
> > On Wed, Mar 10, 2021 at 4:00 PM E. Madison Bray
> > wrote:
> > >
> > > On Tue, Jan 12, 2021 at 11:33 PM tobia...@gmx.de
>
With apologies for replying to such an old message, I should just note that
I fixed this in the most recent Sage Windows release:
https://github.com/sagemath/sage-windows/releases/tag/0.6.2-9.2
On Wed, Dec 16, 2020 at 8:29 PM Matthias Koeppe
wrote:
> This looks like
On Tue, Jan 12, 2021 at 11:33 PM tobia...@gmx.de wrote:
>
>
> For what's worth, + 1 for migrating to github.
>
> The interface is cleaner, it has many more features and integrations, and is
> more active which could attract more contributions. There are a few
> scripts/tools that allow to
link to the source?
If this is about my idea to make the memory allocation functions
"pluggable" that would be done by setting some function pointers to
them, which would be done by third-party Cython code using
MemoryAllocator (there would need to be a C method for setting them).
> On
On Sat, Feb 13, 2021 at 2:16 AM Matthias Koeppe
wrote:
>
> On Friday, February 12, 2021 at 2:35:45 PM UTC-8 vdelecroix wrote:
>>
>> Why make it part of cysignals? The purpose of the memory allocator
>> is quite distinct from cysignals. Merging them look artificial to me.
>
>
> Really?
On Tue, Mar 9, 2021 at 6:13 PM Nathan Dunfield wrote:
>
> An update: I just tried three different binary versions on Linux: The Ubuntu
> 20.04 binary posted at SageMath.org, the sagemath/sagemath:develop Docker
> image, and conda on RHEL 7. None of them "just worked" with "sage -i foo".
>
ge's
> ability on this platform should be a big no-no.
> On the gripping hand (;-)), our current solution for Windows platform rests
> squarely on the shoulders of E. Madison Bray, which accomplishes alone the
> astonishing feat of maintaining what amounts to a port (to an hostile
Ok, it is fixed and re-deployed:
https://github.com/sagemath/sage_trac_plugin/commit/1ff66702f0f1a10a2cca50e9a728493d6ced791e
On Fri, Feb 26, 2021 at 5:31 PM E. Madison Bray wrote:
>
> Let me save you guys some time and say I deployed a new version of the
> sage_trac plug-in today.
Let me save you guys some time and say I deployed a new version of the
sage_trac plug-in today. It worked on all my tests but apparently there is
a weird case where it doesn't.
On Fri, Feb 26, 2021, 16:46 Dima Pasechnik wrote:
>
>
> On Fri, 26 Feb 2021, 15:42 John Cremona, wrote:
>
>> On Fri,
On Wed, Feb 17, 2021 at 3:31 AM Michael Orlitzky wrote:
>
> On Tue, 2021-02-16 at 19:43 +0100, Vincent Delecroix wrote:
> > Dear all,
> >
> > I think we reached a consensus that we should have more and more
> > of the sage source code made as independent Python packages. This
> > effort has
Hi all,
I'm far enough along in its development that I'm happy to announce the
creation of gappy [1], a new Python interface to GAP with no
dependencies on Sage.
It is based on Sage's own sage.libs.gap package, but with a few
possible advantages:
* Having no heavy-weight Sage dependencies, it
On Tue, Jul 14, 2020 at 12:12 AM Rocky Bernstein
wrote:
>
> I think we've beat this to death. So let's agree to disagree.
>
> This kind of thing is not intended for someone like you, but rather, someone
> like me who is just getting started in Sage and CAS and wants to go through a
> number of
In exactly what sense does it not work?
On Wed, Aug 19, 2020 at 9:06 PM Alex G wrote:
>
> Hello Sage Developers,
>
> I have been working on implementing a new class (DynamicalSystem_Berkovich)
> to add to Sage in ticket #29949. For some reason, tab autocompletion does not
> work for any
On Mon, Aug 31, 2020 at 3:56 PM E. Madison Bray wrote:
>
> On Wed, Jul 29, 2020 at 9:02 PM TB wrote:
> >
> > One disadvantage of pickle is safety, in the computer security sense. See
> > the warning at [1] about it, that it is possible to execute arbitrary cod
On Wed, Jul 29, 2020 at 9:02 PM TB wrote:
>
> One disadvantage of pickle is safety, in the computer security sense. See the
> warning at [1] about it, that it is possible to execute arbitrary code during
> unpickling. This of course also happens to be useful in Sage [2].
>
> If it happens that
On Mon, Aug 24, 2020 at 1:36 AM Travis Scholl wrote:
>
> I was using `git-trac` and somehow accidently made 2 tickets:
>
> https://trac.sagemath.org/ticket/30425
> https://trac.sagemath.org/ticket/30426
>
> I don't think tickets can be deleted, but what is the proper etiquette for
> marking one
On Wed, Aug 26, 2020 at 9:56 AM 'Doris Behrendt' via sage-devel wrote:
>
> Hi list,
>
> after searching the web for answers without success, I ask here:
>
>
> What do I have to do to include sage into my environment variables to use
> sage from command line?
>
>
> I found this here:
>
On Thu, May 28, 2020 at 2:03 AM Samuel Lelievre
wrote:
>
> I wish Sage can be made to run with any Python >= 3.6.
>
> See this ticket:
>
> - Support minimal system Python version 3.6
> https://trac.sagemath.org/ticket/29033
>
> I love f-strings and that's a good reason to drop support
> for any
I opened a ticket about this some weeks ago:
https://trac.sagemath.org/ticket/28966
On Fri, Feb 21, 2020 at 5:09 PM Nicolas M. Thiery
wrote:
>
> Hi,
>
> Since Sage uses Python 3, we can finally use unicode symbols for variables:
>
> sage: Φ = lambda λ: λ + 1
>
> But how to input
ri, Mar 6, 2020 at 1:37 PM E. Madison Bray wrote:
>
> I don't have runsnakerun installed right now, but I tried with
> snakeviz [1] and didn't have any particular problems (other than it
> being very slow on load on Firefox just due to the size of the stats
> data). runsnakerun wil
? "It appears to be broken" doesn't help.
[1] https://jiffyclub.github.io/snakeviz/
On Fri, Mar 6, 2020 at 1:29 PM E. Madison Bray wrote:
>
> I don't think there's much special about runsnake in this regard--it
> just uses Python's builin cProfile/pstats modules. The question
I don't think there's much special about runsnake in this regard--it
just uses Python's builin cProfile/pstats modules. The question is
first whether or not plain pstats works.
On Fri, Mar 6, 2020 at 12:25 PM 'Martin R' via sage-devel
wrote:
>
> Dear all!
>
> I need the call graph from a
sorry but it is still not working
>
> On Wed, Feb 19, 2020 at 7:16 PM E. Madison Bray wrote:
>>
>> On Tue, Feb 18, 2020 at 12:17 PM varenyam bakshi
>> wrote:
>> >
>> > I followed the instructions given in sage developer's guide but i am not
>> > b
On Tue, Feb 18, 2020 at 12:17 PM varenyam bakshi wrote:
>
> I followed the instructions given in sage developer's guide but i am not
> being authenticated. I checked it using the basic gitolite commands given in
> the guide
> ssh g...@trac.sagemath.org info
>
> it is showing this error
> please
On Fri, Jan 10, 2020 at 1:03 AM Volker Braun wrote:
>
> * I think its not too difficult to write code that is Python 2.7 + 3.x (for
> high enough x) compatible, so its not a super pressing issue
> * We do have a Python 2 buildbot to test for regressions
> * For semver reasons we should drop
On Tue, Jan 21, 2020 at 5:19 PM Timo Kaufmann wrote:
>
>
>
> Am Freitag, 17. Januar 2020 16:07:08 UTC+1 schrieb E. Madison Bray:
>>
>> On Wed, Jan 15, 2020 at 2:37 AM Matthias Koeppe
>> wrote:
>> >
>> > On Tuesday, January 14, 2020 at 12:01:42 P
On Wed, Jan 15, 2020 at 2:37 AM Matthias Koeppe
wrote:
>
> On Tuesday, January 14, 2020 at 12:01:42 PM UTC-5, Frédéric Chapoton wrote:
>>
>> So here is my proposal.
>>
>> * Starting from now, we allow ourselves to move on, using 9.1 betas and
>> further releases for external python3 updates,
On Tue, Jan 14, 2020 at 9:42 PM Nils Bruin wrote:
>
> On Tuesday, January 14, 2020 at 9:01:42 AM UTC-8, Frédéric Chapoton wrote:
>>
>> So here is my proposal.
>>
>> * Starting from now, we allow ourselves to move on, using 9.1 betas and
>> further releases for external python3 updates, including
On Tue, Jan 14, 2020 at 11:49 AM Dima Pasechnik wrote:
>
> On Sun, Jan 5, 2020 at 7:44 PM Frédéric Chapoton wrote:
> >
> > Hello,
> >
> > I would like to suggest that the sooner we drop Python 2 support the
> > better. We still need to handle the upgrade to ipython7 and the
> > compatibility
On Tue, Jan 14, 2020 at 10:41 AM Timo Kaufmann wrote:
>
> Am Montag, 13. Januar 2020 17:33:56 UTC+1 schrieb E. Madison Bray:
>>
>> On Sat, Jan 11, 2020 at 9:24 AM Antonio Rojas wrote:
>> >
>> > El viernes, 10 de enero de 2020, 14:54:24 (UT
On Sat, Jan 11, 2020 at 9:24 AM Antonio Rojas wrote:
>
> El viernes, 10 de enero de 2020, 14:54:24 (UTC+1), E. Madison Bray escribió:
>>
>> That seems like the obvious approach to me. As it is I've long felt
>> that Sage should be more flexible in its dependencies whe
done. I'm going to add some more stuff to the README, but probably won't
> make any more code changes before v3 unless someone points out an issue.
>
>
> On 1/9/20 6:27 AM, E. Madison Bray wrote:
> >
> > Great, I'll give it a try. It's nice they were able to help you add a
>
On Fri, Jan 10, 2020 at 7:16 PM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> Dear all,
>
> I do maintain Python libraries that depend on Sage and uses the
> Sage doctest framework. I do my best so that the libraries
> install and work on older versions of Sage. However, some features
>
On Fri, Jan 10, 2020 at 3:21 PM kcrisman wrote:
>
>
>
> On Thursday, January 9, 2020 at 6:45:50 PM UTC-5, David Roe wrote:
>>
>> I had a recent discussion asking if there are any good tools for porting
>> Sage code to Python 3. Given the recent discussion about how long we
>> support Python 2,
On Fri, Jan 10, 2020 at 11:49 AM Isuru Fernando wrote:
>
>
> On Fri, Jan 10, 2020 at 3:53 PM E. Madison Bray wrote:
>>
>> On Fri, Jan 10, 2020 at 10:41 AM Timo Kaufmann wrote:
>> >
>> > I have said this before, but I feel like the point was dropped out
On Fri, Jan 10, 2020 at 10:41 AM Timo Kaufmann wrote:
>
> I have said this before, but I feel like the point was dropped out of the
> discussion so I'll stress it again. The major issue here is *not* the
> compatibility of sage's own codebase. A few "from __future__ import"'s are
> not so bad.
On Fri, Jan 10, 2020 at 1:03 AM Volker Braun wrote:
>
> * I think its not too difficult to write code that is Python 2.7 + 3.x (for
> high enough x) compatible, so its not a super pressing issue
> * We do have a Python 2 buildbot to test for regressions
> * For semver reasons we should drop
On Thu, Jan 9, 2020 at 4:28 AM Michael Orlitzky wrote:
>
> On 1/6/20 10:35 AM, E. Madison Bray wrote:
> >
> > Sorry for the delay; I went ahead and created an empty project under
> > our organization and added (I assume) you as a maintainer, so have at
> > i
On Tue, Jan 7, 2020 at 2:16 PM Eric Gourgoulhon wrote:
>
> Le mardi 7 janvier 2020 13:25:04 UTC+1, E. Madison Bray a écrit :
>>
>> On Mon, Jan 6, 2020 at 7:30 PM Eric Gourgoulhon wrote:
>> >
>> > On the other hand, for the end user the major backwards-
On Tue, Jan 7, 2020 at 12:06 AM rjf wrote:
>
> just curious when this ends. Python 4 awaits.
It's already ended. Python 4 is not going to be the major
backwards-compatibility breaker that Python 3 was. It's just going to
be the next release after 3.9, at which point we can also hopefully
On Mon, Jan 6, 2020 at 7:30 PM Eric Gourgoulhon wrote:
>
> Le lundi 6 janvier 2020 14:21:56 UTC+1, E. Madison Bray a écrit :
>>
>>
>> I agree with Nils. There should be at least a one release deprecation
>> period. Also, while I don't think we use any kind of
On Mon, Jan 6, 2020 at 7:23 PM Travis Scrimshaw wrote:
>
> I agree that the Python3 only version of Sage should be called 10.0 given the
> large backwards incompatible changes that result from the Python3 change.
> Furthermore, I also concur that we should release a version 9.1 (on an
>
On Mon, Dec 30, 2019 at 9:41 PM Michael Orlitzky wrote:
>
> On 12/20/19 10:57 AM, E. Madison Bray wrote:
> >
> > I found .spkg archives (which are essentially just zipfiles, or
> > tarballs, I forget which, containing the upstream sources along with
> > some Sage-
On Thu, Jan 2, 2020 at 2:01 PM Oktay Cesur wrote:
>
> Hello Everyone.
>
> I'm a master student and I'm a beginner in a sage. I learned sage for
> symbolic computation course one month ago. I did a presentation about graph
> coloring problem solving with gröbner bases. Main source is this. Now
On Sun, Jan 5, 2020 at 6:22 PM Darij Grinberg wrote:
>
> Aha. The build failure was caused by
> https://trac.sagemath.org/ticket/27444 , exactly as embray's
> comment:34 suggested. Undoing the 1-line change from that branch to
> build/pkgs/fflas_ffpack/spkg-install and recompiling fflas_ffpack
>
On Sun, Jan 5, 2020 at 10:06 PM Nils Bruin wrote:
>
> I think our wiki vetoes that idea. See
> https://wiki.sagemath.org/Python3-Switch :
>
> Compiling with Python 2
>
> After version 9.0, if you really want so, you can still build and use
> SageMath with Python 2, as follows.
>
> make
On Thu, Dec 26, 2019 at 1:10 PM chris wuthrich
wrote:
>
>
> I have a question about the future of srange under python 3, which changes
> the behaviour of range. Probably this has been discussed before but I could
> not find it.
>
> In 9.0.beta10 we have
>
> sage: range(1,3)
> range(1, 3)
>
On Fri, Dec 20, 2019 at 4:53 PM E. Madison Bray wrote:
>
> On Thu, Dec 19, 2019 at 3:04 AM Michael Orlitzky wrote:
> >
> > On 12/18/19 5:19 AM, E. Madison Bray wrote:
> > >
> > > We have already adopted a couple libraries under the umbrella of the
> > &
On Thu, Dec 19, 2019 at 3:04 AM Michael Orlitzky wrote:
>
> On 12/18/19 5:19 AM, E. Madison Bray wrote:
> >
> > We have already adopted a couple libraries under the umbrella of the
> > sagemath org on GitLab:
> >
> > https://gitlab.com/sagemath
> >
>
On Tue, Dec 17, 2019 at 6:38 PM Michael Orlitzky wrote:
>
> SageMath uses a few packages that appear to have been abandoned
> upstream. The most recent example I have in mind is Symmetrica:
>
> http://www.algorithm.uni-bayreuth.de/en/research/SYMMETRICA/
>
> The package's website
On Wed, Dec 18, 2019 at 6:39 AM rjf wrote:
>
> I was trying to come up with a simple example of how this integration program
> claim
> was bogus. Here it is.
>
> Take one of your favorite prime-testing programs and generate
> a list of 10,000 Largish Primes. I don't know how large, but
> say
On Mon, Dec 16, 2019 at 4:39 PM Emmanuel Charpentier
wrote:
> Le lundi 16 décembre 2019 16:13:09 UTC+1, E. Madison Bray a écrit :
>
> [ Bandwidth savings... ]
>
>> > What I mean is that a Windows program can't call a Cygwin program
>> > "transparently"
On Mon, Dec 16, 2019 at 4:01 PM Emmanuel Charpentier
wrote:
>
>
>
> Le lundi 16 décembre 2019 12:06:52 UTC+1, E. Madison Bray a écrit :
>>
>> On Fri, Dec 13, 2019 at 5:16 PM Emmanuel Charpentier
>> wrote:
>> >
>> > Le vendredi 13 décem
On Thu, Oct 10, 2019 at 9:24 PM Dima Pasechnik wrote:
>
> On Debian gp (from pari/gp) links statically to libpari, for performance
> reasons.
Okay, but that's no reason Sage needs to install static libs in
$SAGE_LOCAL/lib. It should only ever be necessary if one package
needs to statically
On Fri, Dec 13, 2019 at 5:16 PM Emmanuel Charpentier
wrote:
>
> Le vendredi 13 décembre 2019 14:12:01 UTC+1, E. Madison Bray a écrit :
>>
>> On Fri, Dec 13, 2019 at 2:05 PM Emmanuel Charpentier
>> wrote:
>> >
>> > While we are already late in t
On Fri, Dec 13, 2019 at 2:05 PM Emmanuel Charpentier
wrote:
>
> While we are already late in the Sage 9 release cycle, Trac#28877, which is a
> (routine) upgrade of R to the current release, may be of benefit.
> For non-R-users : using the latest released R is almost a sine qua non to get
>
On Mon, Dec 9, 2019 at 4:40 PM E. Madison Bray wrote:
>
> On Mon, Dec 9, 2019 at 12:56 PM Dima Pasechnik wrote:
> >
> > On Mon, Dec 9, 2019 at 11:37 AM E. Madison Bray
> > wrote:
> > >
> > > Hi Samuel,
> > >
> > > Coinc
u'll still end up using that one.
This should obviously be avoided. When working with Cygwin you should
generally avoid using anything outside the Cygwin root filesystem
except by explicit intent (e.g. I do use a few programs outside of
Cygwin such as the Microsoft compilers and related tools).
>&g
On Mon, Dec 9, 2019 at 12:56 PM Dima Pasechnik wrote:
>
> On Mon, Dec 9, 2019 at 11:37 AM E. Madison Bray wrote:
> >
> > Hi Samuel,
> >
> > Coincidentally I just commented on this problem in another ticket, and
> > then I saw this post. I'm going to see if
On Mon, Dec 9, 2019 at 4:34 PM E. Madison Bray wrote:
>
> On Mon, Dec 9, 2019 at 8:42 AM Dima Pasechnik wrote:
> >
> > I don't think Cygwin supports paths with spaces in them.
>
> Of course it does. However, it looks like Samuel ran `make configure`
> which is t
On Mon, Dec 9, 2019 at 8:42 AM Dima Pasechnik wrote:
>
> I don't think Cygwin supports paths with spaces in them.
Of course it does. However, it looks like Samuel ran `make configure`
which is trying to run the `bootstrap` script, which since
https://trac.sagemath.org/ticket/27823 calls
Hi Samuel,
Coincidentally I just commented on this problem in another ticket, and
then I saw this post. I'm going to see if I can get my Cygwin
patchbot up and running again. But it would be helpful to have
another.
Thanks for putting out the call. If anyone wants to try there are
On Thu, Dec 5, 2019 at 7:37 AM Samuel Lelièvre
wrote:
>
> Dear Sage-devel,
>
> In mid June 2019 I submitted an application to
> Google's "research credits" programme for
> "Google Cloud Platform".
>
> The project "SageMath continuous integration"
> that I submitted was accepted in early July, and
uld you make a ticket and upload a branch on trac, please ?
>
> Frederic
>
> Le jeudi 23 mai 2019 18:41:04 UTC+2, E. Madison Bray a écrit :
>>
>> Something I've wanted for a long time in the Sage doctest runner is
>> progress bars, so I hacked up a prototype (see screenshot).
By the way, I've been having problems with OpenMP ever since
https://trac.sagemath.org/ticket/27444, if anyone wants to take a look
at that...
On Thu, Nov 7, 2019 at 10:48 PM Dima Pasechnik wrote:
>
> this seems to be related to OpenMP.
>
> are you doing anything special related to this?
>
>
>
On Tue, Nov 12, 2019 at 4:44 PM Simon King wrote:
>
> Dear Erik,
>
> On 2019-11-12, E. Madison Bray wrote:
> > On Fri, Nov 8, 2019 at 11:06 PM Simon King wrote:
> >> While we are at it: Currently, for building the package's documentation,
> >> I use "$MA
On Fri, Nov 8, 2019 at 11:06 PM Simon King wrote:
>
> Hi Erik,
>
> On 2019-11-08, E. Madison Bray wrote:
> > Just to clarify, once more (and please reread my earlier message in
> > this thread regarding what a "DESTDIR install" is and why that is
> > u
On Thu, Nov 7, 2019 at 6:26 PM Simon King wrote:
>
> If sdh_make_install and sdh_pip_install can share a single json file,
> then there would be no need to split the package. I.e., the question is
> whether "sdh_pip_install" will override the json file created by
> "sdh_make_install", or whether
ESTDIR scheme is
used).
> Anyhow, it would make perfect sense to split the package into two, as
> you propose.
I'm not sure. It depends on what "package" means in this case. From
the perspective of Sage it shouldn't matter.
> On Wed, Nov 6, 2019 at 3:55 PM Simon King wrote:
&g
On Mon, Nov 4, 2019 at 2:00 PM Dima Pasechnik wrote:
>
> How does one switch off multiprocessing in docbuild?
> (it's ludicrous not being able to build docs on a VM with 2GB of memory)
The variable you're looking for I think is SAGE_NUM_THREADS=1 (note: I
think it will still fork at least once
On Wed, Nov 6, 2019 at 7:58 AM Simon King wrote:
>
> On 2019-11-05, E. Madison Bray wrote:
> > The generated file `build/make/Makefile` is output by the
> > `./configure` script. In fact, that's its main purpose. When
> > switching branches in this case the best
On Fri, Sep 27, 2019 at 8:01 PM John H Palmieri wrote:
>
> I have been testing new versions of Simon King's p-group cohomology package.
> The current version doesn't work with Python 3, and he has been working
> (#28414) to fix this. My workflow:
>
> check out his git branch
> run ./sage -f
Something that has vexed me since first posting Windows releases to
GitHub is that I would have liked to have at least *some* download
statistics for it, and yet GitHub doesn't display that anywhere on the
website.
However, I was just noodling around in the GitHub API (trying to
automate
On Wed, Oct 2, 2019 at 10:09 AM Simon King wrote:
>
> On 2019-10-02, Kwankyu Lee wrote:
> > Hera:sage-dev$ g version
> > git version 2.23.0
>
> $ git version
> git version 2.7.4
>
> May that be the problem, then?
Probably. That is a quite old version of git (~9 years old). I agree
with you
On Sun, Sep 1, 2019 at 9:14 PM Thierry wrote:
>
> Hi,
>
> it seems to me that Python 3 migration should not only be a syntax
> adaptation (like print('blah')), unicode, or the mitigation of issues
> related to the fact that different objects are not always comparable.
>
> It should also take into
On Wed, Sep 18, 2019 at 11:59 AM Matthias Goerner wrote:
>
>
>
> On Wednesday, September 18, 2019 at 2:11:59 AM UTC-4, Dima Pasechnik wrote:
>>
>> The error in sagenb building is an indication that there was an error
>> earlier on.
>>
>> What does happen if you try starting Sage by doing
>>
>>
On Wed, Sep 18, 2019 at 11:55 AM Dima Pasechnik wrote:
>
> On Wed, Sep 18, 2019 at 10:44 AM E. Madison Bray
> wrote:
> >
> > On Wed, Sep 18, 2019 at 8:11 AM Dima Pasechnik wrote:
> > >
> > > The error in sagenb building is an indication
On Wed, Sep 18, 2019 at 8:11 AM Dima Pasechnik wrote:
>
> The error in sagenb building is an indication that there was an error earlier
> on.
>
> What does happen if you try starting Sage by doing
>
> ./sage
>
> ?
This seems to be happening often enough when there are build issues
(and thus
On Tue, Aug 27, 2019 at 3:19 PM Frédéric Chapoton wrote:
>
> I can create a ticket, but I would like first to be sure that is a real issue.
Do you have any previous benchmarks to compare it to? Even if you
think, for some reason (?) that it's "too slow" I don't know that it's
that meaningful a
Configure issues aside, the main reason for the original problem is that
the system's PARI is built with multi-threading support, whereas in Sage we
build PARI (and by extension its dependencies) without multi-threading
support.
Perhaps we should change that. The major known issue with using
I know one of them is an old Docker patchbot I was running for a long
time. At some point it seems to have gotten stuck. I will see if I
can kill it off once and for all and start a new one from a more
recent Docker image.
On Wed, Aug 21, 2019 at 2:55 AM Kwankyu Lee wrote:
>
> Hi,
>
> It seems
On Sun, Aug 18, 2019 at 5:58 AM TB wrote:
>
> On 13/08/2019 13:55, E. Madison Bray wrote:
> > On Tue, Aug 13, 2019 at 11:28 AM Simon King wrote:
> >>
> >> Hi,
> >>
> >> I am sorry for the late answer (and I am a bit surprised that nobody
On Tue, Aug 13, 2019 at 11:28 AM Simon King wrote:
>
> Hi,
>
> I am sorry for the late answer (and I am a bit surprised that nobody
> else answered before).
>
> I believe it is somehow useful to have such a feature when developing a
> large piece of new code (so that one can do a relevant subset
t; >>
>> > >> >> ld: file not found: /usr/lib/system/libsystem_darwin.dylib for
>> > >> >> architecture x86_64
>> > >> >>
>> > >> >> which indicates that your Xcode installation is somewhat broken.
it just out of curiosity as to exactly what changed
but I couldn't find it.
Nevertheless, it seems as long as you have push permissions to a branch you
can also retry a pipeline on that branch, which I'd have assumed all along
would seem reasonable...
> On Friday, August 2, 2019 at 11:14:24 AM UT
On Fri, Aug 2, 2019 at 5:45 PM Nils Bruin wrote:
>
> On Friday, August 2, 2019 at 2:47:04 AM UTC-7, E. Madison Bray wrote:
>>
>> As I have written before, pickle is not an appropriate format for
>> long-term stable serialization, and never has been, as it is
>> inh
On Sat, Jul 27, 2019 at 8:09 AM Travis Scrimshaw wrote:
>
> Hi Pavel,
>It looks pretty good overall, and it would be really nice to get the
> idempotents and representations into Sage. Then on top of that, you can make
> this notebook into a proper tutorial for Sage. Would you be willing to
Hi Sarah,
Unfortunately from that screenshot alone it's impossible to say much
without additional context (e.g. the relevant log files, though in this
case I couldn't even tell you what the relevant log file was).
Did it look like it failed during the documentation build? E.g., did it
output
MMV, naturally...)
> >> >>
> >> >>
> >> >> On Wed, Aug 7, 2019 at 6:15 PM Holley Friedlander
> >> >> wrote:
> >> >> >
> >> >> > Okay here it is. I had to compress it as it was too large to attach
> >> >> > otherwise.
>
On Wed, Aug 7, 2019 at 3:50 PM Jeroen Demeyer wrote:
>
> On 2019-08-07 15:42, E. Madison Bray wrote:
> > What if, at some point, we just make a Sage release that breaks
> > backwards compatibility?
>
> We could, but I don't think that PEP 3141 is worth breaking backwards
&
1 - 100 of 283 matches
Mail list logo
