Re: [sage-devel] Re: Error building Sage on Arch

I installed planarity from Arch's repository. It still doesn't compile. I think, the compiler doesn't recognize de system version of planarity, because it tries to compile it anyway. Benjamín M. Moraga El vie, 23 may 2025 a las 13:47, Dima Pasechnik () escribió: > On Fri, May 23, 2025 at 11:46 

[sage-devel] Error building Sage on Arch

m. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/f0e3aff0-57fd-4359-962e-a2b5a33842f6n%40googlegroups.com. Using cached file /home/benjamin/Sage/sage/upstream/planarity-3.0.1.0.tar.gz Setting up build directory /home/benjamin/Sage/sage/local/var/tmp/sage/build/planari

[sage-devel] python-flint 0.7.0 released

osta Frédéric Chapoton Oscar Benjamin Tom Hubrecht Changes The full changelog is in the README: https://github.com/flintlib/python-flint?tab=readme-ov-file#070 The documentation is now hosted on readthedocs: https://python-flint.readthedocs.io/en/latest/ There are a lot of

Re: [sage-devel] Re: On `Ideal.groebner_basis(algorithm='singular:stdfglm')`

On Wed, 16 Oct 2024 at 16:45, Nils Bruin wrote: > > On Wednesday 16 October 2024 at 06:43:30 UTC-7 Georgi Guninski wrote: > > sage: Kx.=QQ[] > sage: I=Ideal([x*y]) > sage: gb=I.groebner_basis(algorithm='singular:stdfglm') > > TypeError: Singular error: > ? The ideal i has to be 0-dimensional > > I

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

On Wed, 9 Oct 2024 at 18:15, Marc Culler wrote: > > On Wednesday, October 9, 2024 at 9:32:27 AM UTC-6 Gonzalo Tornaría wrote: > > > As far as I know, cysignals is another instance of a component originally > > developed for sagemath, about maybe 20 years ago, then separated into a > > standalone

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

> > On Tuesday 8 October 2024 at 13:20:54 UTC-7 marc@gmail.com wrote: > > On Tuesday, October 8, 2024 at 1:23:55 PM UTC-6 Nils Bruin wrote: > > > Pypi packages have a default size limit of 100MB per file and 10GB per > > project. > > As you're pointing out, sage still fits within 10GB in sourc

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

On Mon, 7 Oct 2024 at 20:19, Dima Pasechnik wrote: > > Mind you, Mathematica (!) bundles Flint (which is GPL, and depends on > GPLd libraries). FLINT is LGPL as are its dependencies GMP and MPFR. I'm no expert on license terms but Wikipedia says: The main difference between the GPL and the LGPL

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

On Mon, 7 Oct 2024 at 06:05, Kwankyu Lee wrote: > > On Monday, October 7, 2024 at 12:24:04 AM UTC+9 marc@gmail.com wrote: > > > I would say that the motivation is to make it possible for a developer to > > include a self-contained portion of sage in a separate project without > > having to m

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

On Wed, 2 Oct 2024 at 18:16, Matthias Koeppe wrote: > On Tuesday, October 1, 2024 at 10:54:36 PM UTC-7 axio...@yahoo.de wrote: >> >> What do you have in mind people would do with just the stuff in >> `categories`? > > As the dependency diagram shows -- it works as the common dependency of > va

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

On Sun, 29 Sept 2024 at 00:22, Matthias Koeppe wrote: > > On Saturday, September 28, 2024 at 12:28:30 PM UTC-7 axio...@yahoo.de wrote: > > I could also imagine to have three layers: > > * a core distribution with absolutely minimal dependencies and only > dependencies which have proved stable on

Re: [sage-devel] Re: QQbar(-1)^(1/3) != AA(-1)^(1/3)

On Wed, 4 Sept 2024 at 11:06, Kwankyu Lee wrote: > > On Wednesday, September 4, 2024 at 1:41:30 PM UTC+9 Nils Bruin wrote: > > ... it may well depend on whether you're more algebraically or analytically > oriented. > > > Yes. That may be a way to reconcile the conflicting views. > > We may explic

Re: [sage-devel] Re: QQbar(-1)^(1/3) != AA(-1)^(1/3)

On Tue, 3 Sept 2024 at 09:09, Dima Pasechnik wrote: > > Would it be better to hold a vote to decide on the ways to deal with this > issue, rather than on this particular PR? > Namely, the alternatives are > > 1) do nothing > 2) bring AA in line with Python > 3) bring RR in line with AA What does

[sage-devel] Re: Proposal: allow commutative_dga package to include degree zero terms

tative_dga.html#sage.algebras.commutative_dga.DifferentialGCAlgebra_multigraded > > > > El domingo, 18 de agosto de 2024 a las 7:27:20 UTC+2, Benjamin McMillan > escribió: > >> Ah, it would make it harder to compute cohomology. I haven't run into >> that probl

[sage-devel] Re: Proposal: allow commutative_dga package to include degree zero terms

> each bigrade (and hence we can compute the bigraded cohomology), but the > algebra structure would be the one you expect, and if you ignore the second > index in the grading, you get the grading you expect. > El sábado, 17 de agosto de 2024 a las 10:27:20 UTC+2, Benjamin McMi

[sage-devel] Proposal: allow commutative_dga package to include degree zero terms

I would like to propose a simple but large improvement to the commutative_dga package. In short, one currently cannot use the package to create graded commutative algebras that include non-closed degree 0 terms. (For example, this exclude the package from being used for the algebra of differenti

Re: [sage-devel] Removing the backend for mpmath provided by Sage

I find it quite difficult to understand the Sage code so I can't really review the PR. I will say though that I think that this is an important change to make. Both SymPy and Sage reach deeply into mpmath's internals which means that mpmath itself is hamstrung when it comes to future improvements.

Re: [sage-devel] Any tips for Maxima migrating to GitHub

ub > Enterprise server (you can install it for free and use for a month or > so - you'd need a Linux server to run it on). > > HTH, > Dima > > > > > On Thu, Jul 11, 2024 at 5:50 PM Oscar Benjamin > wrote: > > > > Hi all, > > > >

[sage-devel] Any tips for Maxima migrating to GitHub

Hi all, There have been some discussions and tentative attempts to migrate Maxima from SourceForge to GitHub e.g.: https://sourceforge.net/p/maxima/mailman/message/58794267/ I'm wondering how Sage managed to migrate issues from trac to GitHub while still preserving things like who is the author o

Re: [sage-devel] Re: Python version support for SymPy/Sage

Thanks Matthias. On Wed, 5 Jun 2024 at 19:32, Matthias Koeppe wrote: > On Wednesday, June 5, 2024 at 5:31:30 AM UTC-7 Oscar Benjamin wrote: > > > Ordinarily SymPy would have dropped support for Python 3.8 by now > > anyway regardless of SPEC 0 or NEP 29. I can't

[sage-devel] Python version support for SymPy/Sage

Hi all, My question here is: would it be problematic for Sage if SymPy were to follow SPEC 0/NEP 29 which would mean dropping support for older Python versions more quickly? We are about to release SymPy 1.13 which will support Python 3.8 to 3.13. It has been asked on the SymPy mailing list wheth

Re: [sage-devel] wasm

> > Since I am not a programmer and nobody in my team is a mathematician (so my > > developers don't know Sage), I kindly ask on this list for any hints how we > > could proceed? > Sage mainly uses other open source C libraries to carry out these > factorizations, so you would need to be able t

Re: [sage-devel] wasm

Hi Doris, I believe some parts of Sage can be used in WASM (via pyodide) but others cannot so I am not sure if it is possible to get the functionality that you want from Sage in WASM. It is however possible to use SymPy in WASM (via pyodide) as demonstrated here using JupyterLite: https://live.sy

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Wed, 24 Apr 2024 at 15:37, Marc Culler wrote: > > I think that CyPari ;and CyPari2 provide a relevant example. > > Some background ... CyPari is a PyPi package with binary wheels which > predates and was the starting point for Sage's cypari2 (hence the 2 in the > name). The basis for CyPari

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Tue, 23 Apr 2024 at 15:27, Marc Culler wrote: > > The projects that will really benefit from modularization will be those that > provide their own limited mathematical context. Developers of such projects > will be able to choose which parts of Sage are relevant to their specific > context.

Re: [sage-devel] Re: Degree of the zero polynomial ring for `LaurentPolynomialRing`

On Fri, 1 Mar 2024 at 11:51, 'Martin R' via sage-devel wrote: > On Friday 1 March 2024 at 12:15:36 UTC+1 John Cremona wrote: > On Fri, 1 Mar 2024 at 11:03, Dima Pasechnik wrote: > > OTOH, setting the degree of 0 to be -oo has an obvious advantage: it > automaticlly gives mathematically correct d

Re: [sage-devel] Re: Degree of the zero polynomial ring for `LaurentPolynomialRing`

On Fri, 1 Mar 2024 at 11:15, John Cremona wrote: > > On Fri, 1 Mar 2024 at 11:03, Dima Pasechnik wrote: >> >> On Fri, Mar 1, 2024 at 10:24 AM John Cremona wrote: >>> >>> On Fri, 1 Mar 2024 at 10:04, Dima Pasechnik wrote: On 1 March 2024 09:07:26 GMT, 'Martin R' via sage-deve

Re: [sage-devel] Re: Degree of the zero polynomial ring for `LaurentPolynomialRing`

I recently reviewed cases in the sympy polys code that handle the degree of a zero polynomial: https://github.com/sympy/sympy/pull/25784 My conclusion is that it is sometimes useful that deg(0) < deg(p) for p != 0 but otherwise it is not really possible to use the value of deg(0) for anything mean

Re: [sage-devel] Incorrect result for `sum(1/factorial(n**2),n,1,oo)`

Maxima's simplify_sum function produces something similar looking: (%i4) load("simplify_sum"); (%o4) "/usr/share/maxima/5.45.1/share/solve_rec/simplify_sum.mac" (%i5) sum(1/factorial(n^2), n, 1, inf), simpsum; (%o5) 'sum(1/(n^2)!,n,1,inf) (%i6) simplify_sum(%); 1/'product(n^2+%,%,1,2*n+1) non-ra

Re: [sage-devel] Re: Exception in sum((4*n+1)/factorial(n),n,1,oo)

The NoneType error is presumably a bug in the sage wrapper code. Possibly related is that Maxima cannot compute the sum with its default algorithm. It does have a simplify_sum function that can do it though: (%i19) load (simplify_sum); (%o19) "/usr/share/maxima/5.45.1/share/solve_rec/simplify_sum.

[sage-devel] python-flint 0.6.0 released

Hi all, Yesterday I pushed a new release of python-flint version 0.6.0 to PyPI. I expect that this release will appear in conda soon as well. The new release can be installed with pip install --upgrade python-flint As in previous releases there are binary wheels available for CPython 3.9-3.12

Re: [sage-devel] Re: Sage CI Failing in SymPy GitHub Actions

On Sun, 24 Sept 2023 at 22:10, Oscar Benjamin wrote: > > > On Sunday, September 24, 2023 at 11:46:05 AM UTC-7 Oscar Benjamin wrote: > > > >> Where would I send the PR for the Sage doctests? > > On Sun, 24 Sept 2023 at 20:48, Matthias Koeppe > wrote: > >

[sage-devel] python-flint 0.5.0 released

Hi all, Earlier today I pushed a new release of python-flint version 0.5.0 to PyPI. I expect that this release will appear in conda soon as well. The new release can be installed with pip install python-flint There are binary wheels available for CPython 3.9-3.12 for Windows, OSX (intel and a

Re: [sage-devel] Re: Our github checks...

On Mon, 16 Oct 2023 at 23:22, Kwankyu Lee wrote: > > On Tuesday, October 17, 2023 at 12:50:27 AM UTC+9 tobia...@gmx.de wrote: > > I've now set some of the github checks as "required", so they get a small tag > in the checks list. That should take care of (2). > > I am not sure if that helps or ma

Re: [sage-devel] Re: Sage CI Failing in SymPy GitHub Actions

On Sun, 24 Sept 2023 at 22:43, Matthias Koeppe wrote: > > On Sunday, September 24, 2023 at 2:10:26 PM UTC-7 Oscar Benjamin wrote: > > > On Sunday, September 24, 2023 at 11:46:05 AM UTC-7 Oscar Benjamin wrote: > > > >> Where would I send the PR for the Sage doctests?

Re: [sage-devel] Re: Sage CI Failing in SymPy GitHub Actions

> On Sunday, September 24, 2023 at 11:46:05 AM UTC-7 Oscar Benjamin wrote: > >> Where would I send the PR for the Sage doctests? On Sun, 24 Sept 2023 at 20:48, Matthias Koeppe wrote: > > I've added this to ci-sage.yml to explain what to do: > > # To

Re: [sage-devel] Re: Sage CI Failing in SymPy GitHub Actions

On Sun, 24 Sept 2023 at 18:47, Matthias Koeppe wrote: > > PR https://github.com/sympy/sympy/pull/25728 updates the workflow. Apologies > for not submitting this fix earlier. > PRs updating the Sage doctests for changes in SymPy are very welcome. Thanks Matthias. Where would I send the PR for th

Re: [sage-devel] Re: Sage CI Failing in SymPy GitHub Actions

On Sun, 24 Sept 2023 at 09:50, Dima Pasechnik wrote: > > On Sun, Sep 24, 2023 at 9:21 AM Tirthankar Mazumder > wrote: > > > > Sorry to resurrect such an old thread, but the Sage CI is failing for SymPy > > again. This time, it looks to me like the issue is the fact that GitHub > > Actions is tr

Re: [sage-devel] Python return types

On Wed, 6 Sept 2023 at 18:24, John H Palmieri wrote: > > For a while now, Python has allowed return types to be specified in > signatures: > > def f() -> int: > > It is my understanding that this doesn't actually do any error-checking or > type-checking — see https://docs.python.org/3/librar

Re: [sage-devel] remove definitions of __ne__?

On Sat, 2 Sept 2023 at 12:43, 'Martin R' via sage-devel wrote: > > Actually, it seems that I have already found an instance of the problem you > describe, except that I do not understand it. > > In sage/algebras/jordan_algebra.py we have two "def __ne__", one in > JordanAlgebraSymmetricBilinear

Re: [sage-devel] remove definitions of __ne__?

On Sat, 2 Sept 2023 at 12:15, 'Martin R' via sage-devel wrote: > > On Saturday, 2 September 2023 at 11:39:12 UTC+2 Oscar Benjamin wrote: > > On Sat, 2 Sept 2023 at 08:44, 'Martin R' via sage-devel > wrote: > > ... > > It is easy for this sort of

Re: [sage-devel] remove definitions of __ne__?

On Sat, 2 Sept 2023 at 08:44, 'Martin R' via sage-devel wrote: > > If I understand correctly, in python3 it is no longer necessary to implement > __ne__, if it is simply the negation of __eq__. > > There are currently about 200 definitions of the form > > def __ne__(self, other): > re

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

On Fri, 26 May 2023 at 16:19, William Stein wrote: > > On Fri, May 26, 2023 at 7:57 AM wrote: > > > a) Sage has a dual role as a library ("project") and as a distribution. > > > NEP > > > 29 was designed for projects, and not for software distributions. > > > > No, Sage is just a project, with l

Re: [sage-devel] Re: Problematic SR interpretation of radicals (and non-integer rational exponents) in Sage.

In the notebook you note that the results returned by sympy "do not check". I suspect this is because sympy's solve function is being called with check=False under the hood: In [43]: x = symbols('x') In [44]: eq = sqrt(x) + cbrt(x) + 2 In [45]: print(solve([eq], [x])) [] In [46]: print(solve([e

Re: [sage-devel] What is the status of sympy in sagemath? In particular the integrator.

On Thu, 27 Apr 2023 at 06:25, 'Martin R' via sage-devel wrote: > > On Wednesday, 26 April 2023 at 21:06:30 UTC+2 Oscar Benjamin wrote: >> >> One thing Sage could do with SymPy's RootSum is to call doit which >> will expand using radical formulae if po

Re: [sage-devel] What is the status of sympy in sagemath? In particular the integrator.

One thing Sage could do with SymPy's RootSum is to call doit which will expand using radical formulae if possible: x**2/(3*a**2 + 3*a*b*x**3) + RootSum(729*_t**3*a**4*b**2 + 1, Lambda(_t, _t*log(81*_t**2*a**3*b + x))) In [37]: x, a, b, _t = symbols('x, a, b, _t') In [38]: expr = x**2/(3*a**2 + 3

Re: Re: [sage-devel] ChatGPT is an expert in SageMath too

On Fri, 21 Apr 2023 at 20:36, William Stein wrote: > > There's is a discussion right now on HN about LLM's trained on code > > https://news.ycombinator.com/item?id=35657982 > > One of the comments https://news.ycombinator.com/item?id=35658118 > points out that most of the non-GPL super permissive

Re: [sage-devel] RealField isn't doing it right

On Sun, 16 Apr 2023 at 15:52, Trevor Karn wrote: > > I don't have much understanding of how floating point arithmetic works, but > the argument > > >If you're writing python code, you should expect 2*0.5 to return a > >float. But if you're learning linear algebra for the first time and > >typing

Re: [sage-devel] RealField isn't doing it right

On Sat, 15 Apr 2023 at 22:39, aw wrote: > >A user should be able to send any argument to a function, and it's the >responsibility of the programmer to make sure one of two things happen: > > (a) the user is given the right answer; > or (b) the user is given no answer and an error message. That i

Re: [sage-devel] OT: google's chatbot Bard is at https://bard.google.com/

On Sun, 26 Mar 2023 at 19:07, William Stein wrote: > > Ok, that "proof" from GPT-4 is pretty absurd nonsense to put it mildly. I > wonder if there will be a new surge in crank math papers this year. Apparently the way that the chat GPT models are trained is that the source data comes from havi

Re: [sage-devel] Github Discussions

On Wed, 8 Feb 2023 at 20:20, William Stein wrote: > > Many thanks for sharing this from the *developer* point of view. I'm very > much thinking about this problem entirely from the end-user-of-sage point > of view (i.e., me right now).Did you also encounter problems using > discussions with s

Re: [sage-devel] Github Discussions

On Wed, 8 Feb 2023 at 16:47, William Stein wrote: > > Hi Sage Devs, > > Any thoughts about enabling "Github Discussions" for SageMath on > Github now? I just want to share my experience of this feature being used in the SymPy GitHub repo because I personally think that enabling it was a mistake.

Re: [sage-devel] Merging fix for github CI

On Wed, 8 Feb 2023 at 13:10, David Roe wrote: > > On Wed, Feb 8, 2023 at 12:23 PM 'Martin R' via sage-devel > wrote: >> >> Why would I need write access to the sagemath repo? >> >> I would have thought that I'd "somehow" (no idea how) take over the branch >> and modify it. Or are pull requests

Re: [sage-devel] Re: Doubts about correctness of `integrate(floor(x)^2,x)`

On Fri, 3 Feb 2023 at 13:57, Georgi Guninski wrote: > > One of the reasons I asked this is to get correct closed form > for stuff like sum/int 2^2^floor(x). > Judging by the discussions, this won't work. The integration part of that is easy and sage can do it for a single integer interval: >>>

Re: [sage-devel] Re: Doubts about correctness of `integrate(floor(x)^2,x)`

On Fri, 3 Feb 2023 at 09:31, Emmanuel Charpentier wrote: > > BTW : > > ``` > sage: a, b = var("a, b") > sage: f(x) = floor(x)^2 > sage: f(x).integrate(x, a, b) > // Giac share root-directory:/usr/local/sage-9/local/share/giac/ > // Giac share root-directory:/usr/local/sage-9/local/share/giac/ > Ad

Re: [sage-devel] Integral of log() and exp() failing the derivative check

On Sat, 21 Jan 2023 at 14:34, Georgi Guninski wrote: > > I got an integral, which fails the derivative check. > > For real positive x, define > f(x)=2^(x - 1/2*I*log(-e^(-2*I*pi*x))/pi - 1/2) > f(x) is just an obfuscation of 2^floor(x) and > for all positive x, f(x) is integer. > Let g(x) be the i

Re: [sage-devel] Doubts about correctness of `integrate(floor(x)^2,x)`

On Sat, 21 Jan 2023 at 06:43, Jonathan Thornburg wrote: > > On Fri, Jan 20, 2023 at 07:16:14PM +0200, Georgi Guninski wrote: > > I have theoretical reasons to doubt the correctness > > of integrals involving `floor`. > > > > The smallest testcases: > > > > sage: integrate(floor(x)^2,x) > > // Giac

[sage-devel] SageMath docker image + mybinder.org

9a2/HEAD. Is there something particular about SageMath's Jupyter notebook configuration that might cause this; any ideas? Best, Benjamin -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receivin

Re: [sage-devel] VOTE: move Sage development to Github

+1 for GitHub. > On 21.09.2022, at 19:23, David Roe wrote: > > Dear Sage developers, > Following extensive discussion, both recently > > (prompted by issues upgrading the trac server) and over >

Re: [sage-devel] Re: On changing Bernoulli(1) to +½

On Mon, 12 Sept 2022 at 22:09, Fredrik Johansson wrote: > > The claim "bernoulli_plus admits a natural generalisation to real and complex > numbers but bernoulli_minus does not" (made elsewhere in this thread) seems a > bit hyperbolic. For B+ this natural generalization is -n*zeta(1-n); for B-

Re: [sage-devel] On changing Bernoulli(1) to +½

On Mon, 12 Sept 2022 at 16:24, davida...@gmail.com wrote: > > > Why don't we create a B+ and a B-? > > This was one of the idea of the ticket > https://trac.sagemath.org/ticket/34521. A new option to the bernoulli > function was added ("plus=False"), giving the option to the user to choose >

Re: [sage-devel] On changing Bernoulli(1) to +½

On Sat, 10 Sept 2022 at 18:49, William Stein wrote: > > On Sat, Sep 10, 2022 at 10:04 AM davida...@gmail.com > wrote: > > > > > I'm curious if the change breaks any code anywhere else in Sage (e.g., > > > maybe for computing q-expansions of modular forms?)... > > > > You guessed right. I did a

[sage-devel] Sage as a python package?

Would it be possible to restructure the SageMath project such that it becomes in the first place a python package? (A package that can be installed with pip in say the system's python.) I believe that as a python package, sage would obtain a much wider user base. Have there been attempts in t

[sage-devel] deprecation_number PluginFailed in #32215

passes 32215 as the ticket number, so I am a bit confused about this. Thanks, Benjamin -- 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-deve

Re: [sage-devel] Re: Sage GSoC 2021 Projects

I have added a project for expanding Sage's asymptotics module to the list which Clemens and I are willing to mentor. Best wishes, Benjamin Travis Scrimshaw schrieb am Dienstag, 23. Februar 2021 um 00:18:20 UTC+1: > Hi Clemens, >Google could look at the projects page at anytime

Re: [sage-devel] Are complex numbers ordered?

One additional problem with the order is that it is not numerically stable. An example where it is currently used in sage is NumberField.embeddings()-function, the roots of the defining polynomial are sorted this way. Due to the possible numerical instability, it is not clear that the order of the

[sage-devel] Possible bug in NumberField's valuation()

n Sage 9.0, Linux Mint 19.2, 64 bit. Thanks, Benjamin -- 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 th

[sage-devel] Symbolic equations and factor

appropriate? (If so, the message needs to be improved, though.) Or would you be ok with changing back to factoring both sides when calling factor on a symbolic equation? Benjamin -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To u

Re: [sage-devel] Doctest in external packages

suggested by both of you, works though. Thank you, Benjamin On Tuesday, August 20, 2019 at 3:19:56 PM UTC+2, vdelecroix wrote: > > You first need to *install* your module. Otherwise your example.py > can not be found by Python (or Sage). You can also hack the > PYTHON_PATH if it is

[sage-devel] Doctest in external packages

No module named example.example". I wonder how to resolve this and what the intended way of testing external packages with doctests is? Copying the example folder into the $SAGE_ROOT/src/bin/ makes things works, but obviously that's not a real solution. I also tried "sage -t --fo

[sage-devel] [JOB] Software Engineering Positions at Galois Inc.

Hi all, It's been quite a while since I posted anything here, but it's great to see the Sagemath community is still humming! I'm working for a company called Galois Inc. now and we have some positions open I thought I'd spam you with in case you or someone you know is on the job market. https

[sage-devel] Re: Evaluation of beta() in Sage 7.2

r fix this any further. ;-) Benjamin Am Dienstag, 14. Juni 2016 10:28:04 UTC+2 schrieb Ralf Stephan: > > On Tuesday, June 14, 2016 at 10:18:01 AM UTC+2, Benjamin Hackl wrote: >> >> This seems to come from this (7.2.beta6): >> >> sage: (-0.9).log_gamma() >&g

[sage-devel] Re: Evaluation of beta() in Sage 7.2

This seems to come from this (7.2.beta6): sage: (-0.9).log_gamma() NaN sage: (-1.9).log_gamma() 1.71621928121964 sage: (-2.9).log_gamma() NaN sage: (-3.9).log_gamma() -0.709468008908392 sage: (-4.9).log_gamma() NaN sage: (-5.9).log_gamma() -4.07365556493664 sage: (-6.9).log_gamma() NaN sage: (-7.9

Re: [sage-devel] Re: no trac mail notifications?

Our mail system alters the subject (probably since today; wasn't like that last Thursday) like this: ***EVENTUELL*SPAM*** [4.979 / 4] Re: [sage-trac] Maybe this helps someone. All the best, Benjamin Am Montag, 20. Juli 2015 19:21:15 UTC+2 schrieb Daniel Krenn: > > Am 2015-07-

[sage-devel] Re: no trac mail notifications?

... might be just here at AAU. I found my notifications in the spam folder. Benjamin Am Montag, 20. Juli 2015 18:00:29 UTC+2 schrieb Daniel Krenn: > > I do not get any trac mail notifications (about changes, etc.). Have > there been any changes to trac lately? > > Best > &g

[sage-devel] Re: residue produces incorrect results

gular expansions for my research, I'll most likely work on it sooner or later anyhow. Thanks for your support! Kind regards, Benjamin -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receivin

[sage-devel] Re: Expression.series() = PowerSeriesRing(SR)?

der(x^2))*(1 + 1*x + Order(x^2)) Kind regards, Benjamin Am Sonntag, 10. Mai 2015 09:10:04 UTC+2 schrieb Ralf Stephan: > > Instead of duplicating power series functionality (existing in rings/) in > Pynac, > where there is momentarily only a skeleton implementation that does not > e

[sage-devel] residue produces incorrect results

ngularity above and would probably require attention from within Pynac itself.] Does anyone have an opinion with respect to this issue? Should we think about a stopgap for the residue -- or even for the series expansion? Kind regards, Benjamin -- You received this message because you are su

[sage-devel] Re: GSoC 2015: 5 projects funded

Thank you very much for the opportunity! I'm looking forward to working on my project! :-) Best wishes, Benjamin Am Montag, 27. April 2015 22:07:46 UTC+2 schrieb Harald Schilly: > > Hello students and welcome to SageMath! This years GSoC funds five > projects: > > (Mult

Re: [sage-devel] Re: doctest failure in dyck_word.py

I had a discussion regarding the use of python integers some time ago with Daniel Krenn. Basically, range and xrange produce Python integers, whereas srange and sxrange (from sage.misc.misc) produce Integers. Also, when dealing with lists, len usually produces Python int's. (Maybe Daniel has s

Re: [sage-devel] Re: doctest failure in dyck_word.py

py passes without error. This is really strange. Benjamin Am Samstag, 18. April 2015 00:13:59 UTC+2 schrieb vdelecroix: > > At least I opened #18244... > > On 18/04/15 00:02, Benjamin Hackl wrote: > > Vincent, did you also upgrade to 6.7.beta0 or 6.7.beta1 from a previous > >

Re: [sage-devel] Re: doctest failure in dyck_word.py

possibilty that the error is random. I will continue to investigate this by running ptestlong a few more times; if I find something out of the ordinary I'll report back here. Benjamin Am Freitag, 17. April 2015 21:38:18 UTC+2 schrieb Benjamin Hackl: > > Strange. I'm also trying

Re: [sage-devel] Re: doctest failure in dyck_word.py

Strange. I'm also trying to find out what triggers the error, no success yet. Jan Keitel also encountered this error (http://trac.sagemath.org/ticket/18237#comment:6) -- and I'm sure that there are others with the same problem. Benjamin Am Freitag, 17. April 2015 21:17:10 UTC

[sage-devel] Re: doctest failure in dyck_word.py

series of doctests (I suppose you ran "make ptestlong" too?) confuses me. Could this point towards something like caching or memory leak? Benjamin Am Freitag, 17. April 2015 19:19:09 UTC+2 schrieb vdelecroix: > > Hello, > > It seems that I am not the only one to hav

Re: [sage-devel] #15846 + testing local changes to upstream-packages?

... turns out that not only SymPy, but also GiNaC has a problem when expanding zeta around 1. However, it is more likely for the error to come from GiNaC -- so I'll do some more investigations, and then report the issue there as well. In any case, thanks for help! Best wishes, Benjami

[sage-devel] #15846 + testing local changes to upstream-packages?

issue upstream to SymPy etc.). Could someone help me with that? Also, is there a way to test how changes to, say, local/lib/python/site-packages/sympy/functions/special/zeta_functions.py affect my sage installation? Thanks! Kind regards, Benjamin -- You received this message because yo

[sage-devel] Asymptotic Expressions in Sage

e would be happy to exchange some thoughts or explain our plan in more detail! :-) Kind regards, Benjamin -- 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

Re: [sage-devel] What are we unable to do right now ?

716, http://trac.sagemath.org/ticket/17693). Let us know if you have an opinion about this, we would be happy to exchange some thoughts or explain our plan in more detail! :-) Benjamin PS: sorry for digging out this old thread, but making a new one seemed to be sort of an overkill. -- You received thi

[sage-devel] Re: Photomath

Hey...that would be great to add this to Sage...Personally, I think a lot better combination would be Sage + cymath.com . Have you used this site? The site does a fantastic job of explaining how to solve problems step by step. On Thursday, October 23, 2014 12:00:52 PM

[sage-devel] Re: network access from projects

William Stein gmail.com> writes: > > > Is there a way to create a local mirror of all of pypi? One can use the bandersnatch package for this: https://pypi.python.org/pypi/bandersnatch -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubsc

Re: [sage-devel] Re: We need a new color?

I will give that a positive review :) -- Benjamin Jones On Sun, Sep 29, 2013 at 11:26 PM, Maarten Derickx < m.derickx.stud...@gmail.com> wrote: > Speaking of xkcd and easter eggs, I have always thought that since sage > already has an xgcd function, we should also have an xkcd

Re: [sage-devel] GSoC project: Mathematical functions library

It would be fantastic for someone to take up the quest on #12289. -- Benjamin Jones benjaminfjo...@gmail.com On Tue, May 28, 2013 at 3:23 PM, Eviatar wrote: > > On Tuesday, 28 May 2013 14:04:24 UTC-7, kcrisman wrote: >> >> >> >> On Tuesday, May 28, 2013 3:17:25

Re: [sage-devel] GSoC project: Mathematical functions library

Awesome! Ping me if you need someone to help with code review. -- Benjamin Jones benjaminfjo...@gmail.com On Tue, May 28, 2013 at 11:48 AM, Eviatar wrote: > Hello, > > I am grateful to have been selected as one of the Google Summer of Code > students for this summer. I will be

Re: [sage-devel] Matplotlib and sage's python

Without building GUI support, it should work to replace show() with savefig('plot.png'), for example. You won't get a window spawned with the plot, but an image on disk. -- Benjamin Jones benjaminfjo...@gmail.com On Tue, May 21, 2013 at 11:30 PM, Julien Puydt wrote: > L

Re: [sage-devel] Re: Public worksheet disabled on sagenb.org

Seems like a reasonable first approximation would be to strip ALL javascript from the worksheet archive. -- Benjamin Jones benjaminfjo...@gmail.com On Wed, May 15, 2013 at 7:05 AM, Volker Braun wrote: > Somebody needs to volunteer to strip out the malicious javascript from the > arch

Re: [sage-devel] Re: Reasons for upgrading

A, and B. D is nice but not essential. -- Benjamin Jones benjaminfjo...@gmail.com On Tue, Apr 30, 2013 at 11:24 AM, john_perry_usm wrote: > I know you said to move along if I don't upgrade, but I would like to > upgrade if it weren't discommended or unreliable, for reasons

Re: [sage-devel] Race condition in singular doctest (#14371) needs review

FWIW, I'm also experiencing some strange issues with doctesting that don't occur in 5.8, but do in all the 5.9.betaX's. I posted about this on the sage-release thread and at #4102. -- Benjamin Jones benjaminfjo...@gmail.com On Fri, Apr 5, 2013 at 4:33 AM, John Cremona wrote:

Re: [sage-devel] Re: a problem in the new permutation groups code (and a solution ?)

On Tue, Mar 26, 2013 at 3:34 AM, Volker Braun wrote: > > > In any case, http://trac.sagemath.org/14291 is about hooking up GAP and > not creating a framework for group actions. So in the interest of a finite > amout of work per ticket, we should probably fall back to only allow > explicitly specif

Re: [sage-devel] Re: a problem in the new permutation groups code (and a solution ?)

Big +1 to framework for explicitly instantiating group actions. -- Benjamin Jones benjaminfjo...@gmail.com On Mon, Mar 25, 2013 at 11:01 PM, tom d wrote: > Specify the action! By making a group action framework, we would also be > providing the possibility of changing the action to som

Re: [sage-devel] a problem in the new permutation groups code (and a solution ?)

It seems to me that the ambiguity arises from the original statement, "the orbit (1,2) under G", not the fact that the domain is non-homogeneous. It's less ambiguous to say directly G.{1, 2} (the orbit of the _element_ {1, 2}) versus G.1 \union G.2 (the orbit of the subset {1, 2}). Then, which grou

Re: [sage-devel] Review needed : short patch exposes a Group method from GAP in Sage

s !! > > Nathann Hi Nathann, I left a comment on the ticket and made myself a reviewer. -- Benjamin Jones -- 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 e

  1   2   >