Thank you! I just made a new release with the pkg-config support
El miércoles, 6 de noviembre de 2024 a las 2:14:24 UTC+1, dim...@gmail.com
escribió:
> Please see https://github.com/miguelmarco/libbraiding/pull/4
>
> On Mon, Nov 4, 2024 at 10:06 PM mmarco wrote:
> >
> > I
I have no experience on that whatsoever, so if you could do ir (or guide me
with it), i would really appreciate it.
El lunes, 4 de noviembre de 2024 a las 17:52:07 UTC+1, dim...@gmail.com
escribió:
> Hi Miguel,
>
> On Monday, November 4, 2024 at 10:15:01 AM UTC mmarco wrote:
>
>
If I add a .pc file to libbraiding, would it interfere with the install
location in the sage distribution?
El viernes, 1 de noviembre de 2024 a las 13:44:14 UTC+1, Michael Orlitzky
escribió:
> On 2024-11-01 04:32:35, Nils Bruin wrote:
> > There is obviously the "package version", but as I now s
How do I fix a version requirement?
El viernes, 1 de noviembre de 2024 a las 8:03:28 UTC+1, Nils Bruin escribió:
> On Thursday 31 October 2024 at 03:55:41 UTC-7 mmarco wrote:
>
> I recently released a new version of libbraiding that exposes new
> functionality, in order to u
I recently released a new version of libbraiding that exposes new
functionality, in order to use those new functions from Sage (see #38887).
However, the CI tests fail because they use the old version (taken from the
system, instead of installing the new spkg).
Which is the right way to procee
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
t; like this to do calculations on cdga with "degree 0" terms?
>
> On Sunday, August 18, 2024 at 12:27:31 AM UTC+9 mmarco wrote:
>
>> The problem with that approach is that, if there are degree zero
>> generators, the homogeneous part of each degree becomes an
The problem with that approach is that, if there are degree zero
generators, the homogeneous part of each degree becomes an infinite
dimensional vector space. And hence, we can't compute a matrix representing
the differential operator in a given degree (which is needed to compute
cohomology).
As I mentioned in the thread that motivated this one, it would be relevant
to stablish if it is possible to move those packages from standard to pip,
while still having a way to install sage without an internet connection.
If the effort is not too much, I think it would make sense to provide tha
Maybe you can get the best of both worlds? I mean: use those packages as
pip packages, but also have a way to download a big tarball with those
packages, and then pip-install them from that local copy?
El domingo, 11 de febrero de 2024 a las 15:50:17 UTC+1, Kwankyu Lee
escribió:
> How about we
s. In
> contrast to just linking to a Wikipedia page for a definition, this could
> be doctested and roundtripped.
>
> Matthias
>
> On Saturday, February 10, 2024 at 8:50:42 AM UTC-8 mmarco wrote:
>
> One question, Matthias: I see that you have proposed a project involving
> i
One question, Matthias: I see that you have proposed a project involving
integration with proof assistants/theorem provers. Just out of curiosity:
how do you envision such integration?
El martes, 6 de febrero de 2024 a las 6:56:44 UTC+1, Matthias Koeppe
escribió:
> Great, thanks a lot, Travis
FWIW, we are working on a python package that partially overlaps sagetex
functionality:
https://framagit.org/pang/texsurgery
El lunes, 6 de diciembre de 2021 a las 19:06:47 UTC+1, Matthias Koeppe
escribió:
> -1 on demoting it from standard. It's tiny, and installing it as part of
> the dist
+1
El martes, 23 de noviembre de 2021 a las 11:31:19 UTC+1, vdelecroix
escribió:
> +1 for using standard and efficient libraries instead of slow and
> buggy sage implementations :-)
>
> Thanks
> Vincent
>
> Le 23/11/2021 à 11:26, Dima Pasechnik a écrit :
> > primecount is a popular C++ library o
I got to make it work, but the code still needs to be checked for memory
leaks or other subtle pointer related issues.
Reviews welcome.
El lunes, 4 de octubre de 2021 a las 18:52:10 UTC+2, mmarco escribió:
>
> I have retaken the work in #16567 to support rings with parameters in
> li
I have retaken the work in #16567 to support rings with parameters in
libsingular.
The ring creation works, but I am stuck with the conversion of coefficients
from sage to singular and back.
The code I have now is cythonized without complains, but then the c
compilation fails with an error ab
That actually worked. Thanks!
El lunes, 5 de abril de 2021 a las 23:29:25 UTC+2, Michael Orlitzky
escribió:
> On Mon, 2021-04-05 at 21:43 +0100, Dima Pasechnik wrote:
> > internet says it might have to do with wrong permissions to /tmp or
> > TMPDIR pointing to a directory with wrong permissions
Don't think that is the case. The error message is different, and also, the
problem persist even after applying the patch.
El lunes, 5 de abril de 2021 a las 23:29:25 UTC+2, Michael Orlitzky
escribió:
> On Mon, 2021-04-05 at 21:43 +0100, Dima Pasechnik wrote:
> > internet says it might have to
it might have to do with wrong permissions to /tmp or
> TMPDIR pointing to a directory with wrong permissions.
>
> On Mon, Apr 5, 2021 at 6:38 PM mmarco wrote:
> >
> >
> > I am getting this kind of error messages when trying to run `make test`
> or `sage -t file.p
I am getting this kind of error messages when trying to run `make test` or
`sage -t file.py`:
Using --optional=build,dochtml,gentoo,kenzo,memlimit,pip,sage,sage_spkg
Doctesting entire Sage library.
Doctesting 4271 files.
Traceback (most recent call last):
File "/home/mmarco/sage/src/bin
I have participated as mentor other years... but this year I just don't
think I have the needed energy.
I think Harald's proposal to pass this year and reconsider the next one
makes sense (sadly).
El domingo, 7 de febrero de 2021 a las 17:54:07 UTC+1, harald@gmail.com
escribió:
> Hi, a wor
I have just published a paper there, with the Sage code to compute minimal
models of GCDA's. So it is certainly possible to publish Sage papers there,
but my impression is that the journal is more geared towards publishing
"external packages" (which might fit with the workflow of systems like
You mean having a function (or global variable) to set which will be the
default backend?
I find that having a workflow consisting on expressions like:
integrate(foo,x,algorithm='giac')
is not specially comfortable, but even then, I prefear it to something like:
set_integration_backend('giac')
+1
Also, I suggest that we consider the possibility of using giac as the
default backend for symbolic integration.
El lunes, 3 de febrero de 2020, 23:52:44 (UTC+1), Samuel Lelievre escribió:
>
> Please vote for making giacpy_sage a standard package. See
>
> - Sage Trac ticket: 28918
> Make g
>
>
> The second may be a bug in the patchbot server itself. I have no time to
> investigate. Maybe the # in the patchbot name is not a good idea (random
> guess) ?
>
>
It looks like that could be the culprit, since It also happens in other
machines. Any idea on how it could be solved?
--
Yo
For completeness, the problem of the log not being sent is also present in
another VM running arch:
https://patchbot.sagemath.org/log/0/Linux/#1%20SMP%20PREEMPT%20Fri,%2029%20Nov%202019%2013:37:24%20+/x86_64/5.4.1-arch1-1/patchbot-arch/2019-12-10%2008:19:07
Maybe some trouble of the patchbo
>
>
> The second may be a bug in the patchbot server itself. I have no time to
> investigate. Maybe the # in the patchbot name is not a good idea (random
> guess) ?
>
> F
>
I see. Is there a command to uninstall a package? or should I edit some
file manually?
I will try avoiding the number in
I am setting up several virtual machines with different distros to run
patchbots on them. In particular I want to use different distros (including
less usual ones) to get more diversity in the patchbot set.
However, I am finding some problems:
A debian machine is returning the following error w
Great, now fflas_ffpack complains about not finding blas
--
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 disc
correct value, and rebuild...
>
> On Wed, Dec 4, 2019 at 4:09 PM mmarco >
> wrote:
> >
> > I am trying to setup several virtual machines to run patchbots (for
> different distros). I am getting the following error when trying to compile
> Sage from source:
>
I am trying to setup several virtual machines to run patchbots (for
different distros). I am getting the following error when trying to compile
Sage from source:
n not be used when making a shared object; recompile with -fPIC
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/
d, 20 Nov 2019 at 18:09, mmarco >
> wrote:
>
>> I see, thanks.
>>
>> Is it a default behaviour?
>>
>
> no, it appears that you have a weird configuration, e.g. I have libblas
> installed systemwide, but things just work.
> Perhaps it is a Numpy bug.
>
I see, thanks.
Is it a default behaviour?
--
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 the
The log shows this:
FOUND:
libraries = ['openblas', 'blas']
library_dirs = ['/home/mmarco/sagep3/local/lib', '/usr/lib64']
include_dirs = ['/usr/include', '/home/mmarco/sagep3/local/include']
language = c
--
FO
I didn't do anything specific to try to use external blas/lapack. How can I
check if sage is trying to?
El miércoles, 20 de noviembre de 2019, 10:01:14 (UTC+1), Dima Pasechnik
escribió:
>
> On Wed, Nov 20, 2019 at 8:26 AM mmarco >
> wrote:
> >
> > Hi,
> >
If all the issues ar solved... sure. I was even surprised that we started
haviong betas of version 9 with python 2 (I assumed that the witch to
version 9 would be mostly about the transition to python 3).
+1
El domingo, 27 de octubre de 2019, 1:58:23 (UTC+2), Volker Braun escribió:
>
> Maybe I
I would be very interested in comparing their results with RUBI.
El viernes, 27 de septiembre de 2019, 21:53:00 (UTC+2), Eric Gourgoulhon
escribió:
>
> Thanks for sharing!
> This looks very promising. I hope we have it in Sage some day.
>
> Eric.
>
> Le vendredi 27 septembre 2019 17:06:31 UTC+2,
I get an Internal Server Error when I try to access the patchbot. In
particular, I can't see patchbot reports for any ticket.
To make sure that it is not a problem with my network: does anybody else
experience the same?
--
You received this message because you are subscribed to the Google G
I think the change you propose is reasonable. However, it sounds like a lot
of work, and the support for python2 ends in just a few months. We should
aim to release a python3 based release that passes all tests before the end
of the year.
Do you think it is reasonable to do these deep changes i
This is now #28415
https://trac.sagemath.org/ticket/28415
El lunes, 19 de agosto de 2019, 13:24:10 (UTC+2), mmarco escribió:
>
> I have been working a bit on some functions to help students do
> integration by hands. Under the hood, they use sympy's integral_steps
> function
Ups, I wrote it wrong. His name is Grayson Jorgenson, not Jayson.
El viernes, 23 de agosto de 2019, 20:59:17 (UTC+2), mmarco escribió:
>
> Jayson Jorgenson implemented resolution of singularities for plane curves
> as a GSoC project a few years ago:
>
>
> https://doc.sa
Jayson Jorgenson implemented resolution of singularities for plane curves
as a GSoC project a few years ago:
https://doc.sagemath.org/html/en/reference/curves/sage/schemes/curves/affine_curve.html
But I guess you are talking about the general case.
IIRC, singular returns the output of the resol
BTW
El martes, 20 de agosto de 2019, 5:44:33 (UTC+2), rjf escribió:
>
> It may be a mistake to combine "help for students learning symbolic
> integration"
> and "symbolic integration" simply because the methods taught to students
> are probably different from the integration algorithms used by co
>
>
> The link below to docs did not work for me until I added an "l' to make
> it html.
>
You are right, sorry for the broken link.
--
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
I have been working a bit on some functions to help students do integration
by hands. Under the hood, they use sympy's integral_steps function (see
[1]), but I am not sure which is the right way to present it. The options I
am considering are:
1) Go full step-by-step integrations, in the spirit
You might be interested in taking a look at tides [1]. It is a library for
integration of ODE's in high precission using precisely automatic
differentiation and Taylor arithmetic. It doesn't use interval arithemtic
(so, no certified computation), but maybe some ideas could be useful.
The way it
>
>
> None of these will really help in this case. Without abs_integrate, you
> get no answer. With abs_integrate, you get the wrong answer. This one
> will probably have to be fixed in Maxima.
>
Going from a wrong answer to no answer is an improvement. So yes, it does
help in this case.
-
The proposal of not using abs_integrate by default, and provide the option
of using it it with an algorithm keyword seems the most logical to me.
El viernes, 22 de marzo de 2019, 16:46:38 (UTC+1), Nils Bruin escribió:
>
> On Friday, March 22, 2019 at 3:00:54 AM UTC-7, Dima Pasechnik wrote:
>>
>>
So the bug is really in the abs_integrate package for maxima? In that case:
is it really worth it to import it by default?
El miércoles, 20 de marzo de 2019, 13:58:46 (UTC+1), Dima Pasechnik
escribió:
>
> On Wed, Mar 20, 2019 at 05:36:59AM -0700, mmarco wrote:
> > I am trying to
I am trying to pinpoint the following bug:
sage: integral(sqrt(1+cos(x)^2),x)
-1/24*sin(3*x) + 1/8*sin(x)
which is incorrect. One would think that maxima is returning a wrong
answer, but if we ask directly to maxima, it leaves the integral as it is:
sage: f = sqrt(1+cos(x)^2)
sage: maxima.int
About that, I dealt with that for a test installation if
jupyterhub/jupyterlab i am working in at my university.
My solution consisted in two parts:
1) Copying the threejs files to a directory where the jupyterhub server can
serve them (in my case, it was /usr/local/share/jupyterhub/static/ )
Is there any essential reason why online=False can not work on nbviewer or
mybinder? If it can be solved, I think it makes more sense to make it work
without breaking the default behaviour when there is no internet available.
El lunes, 11 de febrero de 2019, 18:31:33 (UTC+1), Eric Gourgoulhon
e
ble thing to do - perhaps I
> miss something trvial here...
> 12:13 < phoe> you don't want to use Quicklisp in that case
> 12:13 < phoe> quicklisp operates with the assumption that users can
> download arbitrary stuff into the Quicklisp directory
> 12:14 < pho
gt;
> On Fri, Feb 1, 2019 at 8:32 PM mmarco >
> wrote:
> >
> > Yes, but what I mean is that when you do that, kenzo code is compiled
> into the user's home directory (look under ~/quicklisp). So if there are
> several users in the same machine, it will be com
Dima Pasechnik escribió:
>
> On Fri, Feb 1, 2019 at 4:23 PM mmarco >
> wrote:
> >
> > Thanks for the answers.
> >
> > I just realized that the package I want to install is available by
> quicklisp, so maybe it would be easyer to install it using that.
> &
Thanks for the answers.
I just realized that the package I want to install is available by
quicklisp, so maybe it would be easyer to install it using that.
However I noticed that quicklisp installs evetything in the users home
directory, even if it is called from the sage environment. That woul
I am working in a Kenzo interface/optional package. I managed to load
through the ecl interface, but using asdf, but in order to do that I had to
have it installed in my ~/common-lisp/ directory. As an optional package,
it should be located in some directory of the sage install, that must be
fo
Maybe I could mentor a student, but don't have in mind any specific project
proposal right now. WIll think about it.
El martes, 15 de enero de 2019, 21:28:16 (UTC+1), Harald Schilly escribió:
>
> Hi everyone. This years Google Summer of Code 2019 just started. Should we
> write an application? W
I would be interested in that too, but that sounds like a complex task. I
think one or more GSoC projects could fit into that... and maybe also some
thematic Sage Days.
El jueves, 22 de noviembre de 2018, 11:28:32 (UTC+1), Dima Pasechnik
escribió:
>
> On Thu, Nov 22, 2018 at 9:43 AM parisse >
That is exactly the case: the cocoalib package is just that for the moment:
a way to install cocoalib from sage.
The plan when that was done was to write a cython interface , but that
hasn't been done yet. Since cocoalib is a very big library, I think it
would be a good idea to do so incrementa
Do you know if something similar exists for jupyterlab?
El sábado, 4 de agosto de 2018, 10:56:39 (UTC+2), Volker Braun escribió:
>
> There is a jupyter extension for that, though I haven't tried it...
>
>
> https://github.com/ipython-contrib/jupyter_contrib_nbextensions/tree/master/src/jupyter_con
Ok, let me know if you can verify that libbraiding works on cygwin.
El jueves, 28 de junio de 2018, 17:27:54 (UTC+2), Erik Bray escribió:
>
> On Thu, Jun 28, 2018 at 5:25 PM mmarco >
> wrote:
> >
> > The packages libbraiding and libhomfly have been optional for m
The packages libbraiding and libhomfly have been optional for more than a
year. They provide methods for braids and knots that many people find
useful, so I propose to make them standard packages.
Are you ok with that?
--
You received this message because you are subscribed to the Google Group
What about creating a `is_prime_integer` function? Explicit is better than
implicit, and in that case we leave no ambiguity in the mathematical sense,
but also cover the use case of the casual user.
What i definitely don't want is `.is_prime()` return `True` when it is
applied to an element th
jupyterhub or not.
El domingo, 4 de marzo de 2018, 0:42:43 (UTC+1), Kwankyu Lee escribió:
>
>
>
> On Sunday, March 4, 2018 at 1:17:40 AM UTC+9, mmarco wrote:
>>
>> Thanks, I finally could solve it with a dirty hack:
>>
>> I put the nbextensions inside /usr/local/sha
:27 (UTC+1), Kwankyu Lee escribió:
>
>
>
> On Friday, March 2, 2018 at 12:30:29 AM UTC+9, mmarco wrote:
>>
>> I am trying to install a service to use Sage through the jupyterlab
>> frontend, behind a jupyterhub server.
>>
>> So far, I could get everyt
I am trying to install a service to use Sage through the jupyterlab
frontend, behind a jupyterhub server.
So far, I could get everything to work, even the threejs interactive
graphics on a standalone jupyterlab instance. In order to make it run I
just copied the corresponding nbextension folder
+1
--
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 post to this group, send email to sage-devel@googlegroups.com.
Visit
shcedule.
Best,
Miguel
El martes, 7 de noviembre de 2017, 13:04:00 (UTC+1), Simon King escribió:
>
> Hi Miguel,
>
> On 2017-11-07, mmarco > wrote:
> > - The sage development workflow (Trac, git, doctests...) -> Eric
> > Gourgoulhon
> > - The coercion model &
ells me
> this doesn't happen as often as one wants.
>
> Best,
> Travis
>
> On Wednesday, November 8, 2017 at 2:33:13 AM UTC+10, Jeroen Demeyer wrote:
>>
>> On 2017-11-07 12:26, mmarco wrote:
>> > I have to clarify: Tomer Bauer did not volunteer to give a
I have to clarify: Tomer Bauer did not volunteer to give a talk about
creating extensions; he actually showed interest in learning about it. He
mostly means following this approach:
https://github.com/sagemath/sage_sample
Any takers?
El martes, 7 de noviembre de 2017, 10:32:19 (UTC+1), mmarco
Consdering your offers, I made a temptative assignation of the subjects to
cover:
- The sage development workflow (Trac, git, doctests...) -> Eric
Gourgoulhon
- The coercion model & Implementation of Parents and elements -> Simon King
- The category framework -> Travis Scrimshaw
- Cython &
I have created the wiki page: https://wiki.sagemath.org/days94
Please feel free to edit it if you want to add more information (for
instance, if you want to assign a course to yourself). I will add more
information as we get more details figured out.
Best,
Miguel.
--
You received this mess
Thank you all!
If it is ok with you, I will create a wiki page to keep track of the
organization details. As soon as we can close the dates (maybe next week),
I) will let you know.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
Hello,
We will be organizing the next meeting of the spanish network of computer
algebra in Zaragoza (Spain); the proposed dates are July 4th-6th. As a
satellite event we plan to organize also a Sage Days (right before, or
right after the meeting), in the form of a school oriented to introducin
Indeed. This last GSoC there was some work to include the Rubi integrator
in sympy. That could allow to compute a larger set of integrals (although I
have read that it can be kind of slow). It would be a good idea to consider
which one of these options we should call by default in each case.
This is now #23395 <https://trac.sagemath.org/ticket/23395>
El lunes, 10 de julio de 2017, 13:43:46 (UTC+2), mmarco escribió:
>
> If you used quo_rem, beware that Sage only uses Singular if the
> coefficient ring is a field. So if you define your polynomials over QQ
> instead
we could rely on Singular also for the case of Integers.
El lunes, 10 de julio de 2017, 12:48:55 (UTC+2), mmarco escribió:
>
> It is surprising the difference between singular and Sage, considering
> that Sage mostly relies on Singular for multivariate polynomial arithmetic.
> In
we could rely on Singular also for the case of Integers.
El lunes, 10 de julio de 2017, 12:48:55 (UTC+2), mmarco escribió:
>
> It is surprising the difference between singular and Sage, considering
> that Sage mostly relies on Singular for multivariate polynomial arithmetic.
> In
It is surprising the difference between singular and Sage, considering that
Sage mostly relies on Singular for multivariate polynomial arithmetic. In
the case of divisions, I suspect that it has to do with the fact that Sage
treats division of polynomials as an operation in the fraction field, s
FWIW I have recently written a library that performs certified root
continuation of bivariate polynomials. It makes extensive use of MPFR, and
plan to include it as a Sage package. So, since the goal is to make
certified computations, it would be really nice to have a formal proof of
the underl
I recommend you to start by reading the sage developer guide:
http://doc.sagemath.org/html/en/developer/index.html
It covers all the development process.
I am no expert in Coxeter groups, but from what I see, we already have
support for them in Sage. So I will assume that your software would pr
Does that work on all the platforms supported by anaconda, or is it linux
only?
El jueves, 23 de marzo de 2017, 5:29:31 (UTC+1), Isuru Fernando escribió:
>
> Hi,
>
> Update: With the help of Erik and Julian, we now have all the runtime
> dependencies of sage in conda-forge.
>
> There are some mo
rease the number of cases that we can integrate, the first step
would be to have some support for simplification rules.
El martes, 28 de febrero de 2017, 18:01:58 (UTC+1), parisse escribió:
>
>
>
> Le mardi 28 février 2017 15:57:53 UTC+1, mmarco a écrit :
>>
>> Many RUBI r
sqrt(polynomial of degree 2). But perhaps I misunderstand Rubi, and it
> does that inside Mathematica?
>
> Le mardi 28 février 2017 10:50:50 UTC+1, mmarco a écrit :
>>
>>
>>> Back to the original proposal. Certainly rules can't catch all cases
>>> either
>
>
> Back to the original proposal. Certainly rules can't catch all cases
> either. Doesn't this call for a combined approach? As soon as we have rules
> in Sage they should be called before the best algorithm we have. The
> default then IMO should be "special rules + Maxima" instead of Maxima
>
>
>
> I think that it might be possible to wrile (in Python ?) a "Ruby rules
> compiler" that could use our (rudimentary) wildcard facility to effect
> those substitutions. A possible companion would be a "Mathematica compiler"
> able to translate a Mathematica Integrate statement and transla
UTC+1, mmarco wrote:
>>
>> cdef extern from "my_library.h":
>> mpfr_t* my_function (mpfr_t *_coef)
>>
>
>
> That isn't exactly idiomatic C++, but ok
>
>
> /home/mmarco/sage/local/lib/python2.7/site-packages/IPython/core/ultratb.pyc
>
llocation at all.
>
> Le 05/02/2017 à 11:40, Vincent Delecroix a écrit :
> > If you had a look at the code I provided you can check that what you did
> > is very wrong.
> >
> > mpfr_t is already an array. The type "mpfr_t * x" make no sense at all.
>
-
UnicodeDecodeErrorTraceback (most recent call last)
/home/mmarco/sage/local/lib/python2.7/site-packages/IPython/core/
interactiveshell.pyc in run_code(self, code_obj, result)
2896 if result is not None:
2897 result.error_in_exec = s
I am working in a C++ library that provides some certified homotopy
continuations. It provides a function that, takes as input a list of
floating point numbres and returns another such list.
I am having a lot of trouble trying to write a sage-cython interface for
mpfr floats (the version for d
I am not sure I will have time to be a mentor this year, but I would like
to propose porting rubi to sage:
http://www.apmaths.uwo.ca/~arich/
It is a series of rules (over 6000) to be applied to symbolic expressions
in order to get their primitive. The results they produce are better than
the M
If you provide several binaries, I think it would be wise to advertise the
lowest common denominator as the "standard" one, so it works for every
user.
El miércoles, 14 de diciembre de 2016, 12:59:13 (UTC+1), Erik Bray escribió:
>
> On Wed, Dec 14, 2016 at 12:47 PM, Erik Bray > wrote:
> > On
On Thursday, December 8, 2016 at 8:41:55 PM UTC, mmarco wrote:
>>
>> If I am not mistaken, the reference manual is automatically built from
>> the docstrings in the source code files... which are GPL. How does that
>> affect the resulting documentation?
>>
>
> w
If I am not mistaken, the reference manual is automatically built from the
docstrings in the source code files... which are GPL. How does that affect
the resulting documentation?
El jueves, 8 de diciembre de 2016, 17:17:19 (UTC+1), Dima Pasechnik
escribió:
>
> As pointed out in
> https://group
If this is of any help, this is what I use:
https://github.com/miguelmarco/pykdedebugger
El sábado, 26 de noviembre de 2016, 8:25:02 (UTC+1), Maxie Schmidt escribió:
>
> I've been looking at GUI-based (or at least text-GUI-based) python
> debuggers to help with fixing bugs in a larger python cod
The way I would handle those cases, is by raising an exception. The same
way that you raise an exception when the software is not able to give any
other answer that you might ask.
El martes, 15 de noviembre de 2016, 8:22:15 (UTC+1), tdumont escribió:
>
> When developing a software which aims to
Both results are equivalent in this case (the given charts actually differ
only by a change of coordinates), but I am not sure why the difference has
appeared. I will try to have a look at it in the following days (although
don't have much time available lately). Is it possible that Singular 4
Since we are talking about the wiki... I would propose to use another
default theme. From my perspective, the default theme looks much worse than
other possibilities:
https://moinmo.in/ThemeMarket
Even if we don't want to install anything, just changing the default to the
righsidebar one (alre
I am really happy to see her using (and endorsing) Sage. Apparently she
will publish some code in November. I am not completely sure she is talking
about lattice based crypto. There are other possibilities, (code-based,
isogenies...) for which Sage could also be useful.
Maybe this will attract
1 - 100 of 634 matches
Mail list logo
