Le 13/09/2015 01:36, Vincent Delecroix a écrit :
It would indeed be cool to have an option to change interactively the
precision...
preparser.set_precision?
or simply
set_precision?
Vincent
I can look at this and propose an implementation...
Thanks!
t.
On 12/09/15 19:49, David Roe wrote:
Hi Volker, hi Jeroen,
On 2015-09-12, Jeroen Demeyer wrote:
> On 2015-09-12 23:36, Volker Braun wrote:
>> See the usage of OptionalExtension in src/module_list.py
>
> To add to this answer: an OptionalExtension is *always* Cythonized, i.e.
> Cython is run to generate a .c file. However, it is onl
>
>
>> R has the resources to do this, and is very picky about
>>
>
> R has vastly more resources than us to put mildly.
>
>
To put it mildly :)
I apologize - It was a mistake how we released sage and broke a large
> number of spkg's just because we didn't want to include a backwards
> compat
Hi William.
On Sat, Sep 12, 2015 at 7:57 PM, William Stein wrote:
>
>>
> Could you build both and decide at runtime? Which is used in recent
> versions of mma?
>
No, because older versions of Mathematica do not ship with the WSTP
headers. It looks like both are shipping with new versions of
On Saturday, September 12, 2015, Robert Jacobson
wrote:
> I want to give an update regarding my attempt to "permanently" solve the
> Mathematica interface problem with my interface to Mathematica (
> https://github.com/rljacobson/MathLine). I think my code is fine, but I'm
> embarrassed to say th
I want to give an update regarding my attempt to "permanently" solve the
Mathematica interface problem with my interface to Mathematica (
https://github.com/rljacobson/MathLine). I think my code is fine, but I'm
embarrassed to say that I can't figure out how to write a cross-platform
build scrip
It would indeed be cool to have an option to change interactively the
precision...
preparser.set_precision?
or simply
set_precision?
Vincent
On 12/09/15 19:49, David Roe wrote:
One approach would be to change "RealNumber('%s')" % num on line 739
of sage.repl.preparse to "RealNumber('%s',min
One approach would be to change "RealNumber('%s')" % num on line 739
of sage.repl.preparse to "RealNumber('%s',min_prec=1000)" % num.
David
On Sat, Sep 12, 2015 at 12:24 PM, Thierry Dumont
wrote:
> I have a program with a lot of floating point constants/variables (this is a
> translation of a C++
On 2015-09-12 23:36, Volker Braun wrote:
See the usage of OptionalExtension in src/module_list.py
To add to this answer: an OptionalExtension is *always* Cythonized, i.e.
Cython is run to generate a .c file. However, it is only compiled if a
condition is satisfied, which is usually a package
See the usage of OptionalExtension in src/module_list.py
On Saturday, September 12, 2015 at 9:48:34 PM UTC+2, Simon King wrote:
>
> Is it possible to have Cython files in src/sage/... that are only
> compiled if a certain optional package is installed? That's not the same
> as a dependency: A de
Hi!
Suppose we have a C-library (as part of MeatAxe), which is provided
by an *optional* package. I would like to have a Cython wrapper in the
SageMath library.
How can that be done? If there is a Cython file in src/sage/ that uses
the optional package, then its compilation will fail, unless the
Hi Nathann,
On 2015-09-12, Nathann Cohen wrote:
>> Or how does it
>> work? The developer manual doesn't seem to mention it.
>
>
> True, we should probably add a section about that. Though it will probably
> change soon because of Volker's "fileserver.sagemath.org" (which seems down
> at the m
> Yes, change the authors field.
Done.
Can you edit the file sage.ris that appears at the bottom of that page ?
http://wiki.sagemath.org/Publications_using_SAGE#preview
Thanks,
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubs
On Saturday, September 12, 2015, Nathann Cohen
wrote:
> > +1 for "SageMath Mathematics Software"
>
> On the same subject: hadn't we agreed to change the "authors" field to
> "The SageMath developers" ? The wiki page still shows a "William Stein
> and others".
>
>
Yes, change the authors field.
On Saturday, September 12, 2015, kcrisman wrote:
> I thought some patchbots did test optional packages on a more or less
>>> regular
>>> basis?
>>>
>>
>> No, the build/patchbots only test standard packages. Of course we would
>> be happy to have you volunteer as the person in change of testing al
I have a program with a lot of floating point constants/variables (this
is a translation of a C++ program).
Nowadays -by default- all these values live in RealField(53).
But, as my problem is a bit ill conditioned, I would like to compute in
higher precision, say in RealField(1000).
Is there
On Saturday, September 12, 2015 at 5:18:38 PM UTC+2, Simon King wrote:
>
> Shall I indicate on Trac where to find the
> upstream sources, and the reviewer downloads them manually, and once the
> ticket gets a positive review, the sources will be put on a Sage server,
> where they would then auto
Hello !
So, what is the procedure? Shall I indicate on Trac where to find the
> upstream sources, and the reviewer downloads them manually, and once the
> ticket gets a positive review, the sources will be put on a Sage server,
> where they would then automatically be downloaded from?
Ideally
Hi!
I thought that new-style packages would obtain the sources directly from
upstream. So, I expected that some file in build/pkgs/foo/ provides the
URL for foo's sources, and "sage -i foo" would automatically download
sources from there (if not already present).
But apparently I was mistaken. Th
> The new thing where all installed optional
> packages are tested is a good start, it's clearly already helped.
Here is a (stalled) attempt at pushing it further. Needs volunteers.
http://trac.sagemath.org/ticket/18904
Nathann
--
You received this message because you are subscribed to the Goog
Just FYI, there's a long discussion going on right now on python-ideas
mailing list about the standard random number generator in python, and
whether it would be a better idea to have cryptographically secure
random number generation by default. I'm mentioning it here since
there's likely peop
>
> I thought some patchbots did test optional packages on a more or less
>> regular
>> basis?
>>
>
> No, the build/patchbots only test standard packages. Of course we would be
> happy to have you volunteer as the person in change of testing all optional
> packages.
>
>
R has the resources to
Hello Dima,
are you using the option --skip-base ?
Because your patchbot is again failing on the bare sage, see top of
http://patchbot.sagemath.org/ticket/0/
and should therefore not test any other ticket, unless you choose the above
option, which is not recommended.
Concerning why your patch
On Saturday, September 12, 2015 at 9:48:38 AM UTC+2, Simon King wrote:
>
> For the record: I think ANY backward incompatible internal change that
> *can*
> be covered by a deprecation warning (thus, changed import locations,
> changed function names or argspecs, etc) *has* to be covered by a
>
Some details...
1. copying to upstream; 2. creating new checksum; 3. make
>
This works only sometimes. When it does not work then
sage -f pynac; touch build/pkgs/pynac/checksums.ini; make
will work, as I just found out.
--
You received this message because you are subscribed to the Google Grou
On 2015-09-12 10:24, Ralf Stephan wrote:
In the recent beta something seriously changed
That is certainly true, I'll write a more detailed post later. There are
more changes coming.
However, even in 6.9.beta6, "sage -f pynac" still works for me, so you
need to give more details for me to repr
On 2015-09-12 09:48, Simon King wrote:
All versions from 2.1.2 till now were at least partially
motivated by coping with backward incompatible changes.
I am probably responsible for several of these backward incompatible
changes. However, they were changes to the basic Sage infrastructure,
li
In the recent beta something seriously changed such that there is
no longer a reliable method for the local developer to recompile
a package where the tarball changed (not the version no.).
Example: testing a new pynac tarball involved until now
1. copying to upstream; 2. creating new checksum; 3.
Hi John,
On 2015-09-12, John H Palmieri wrote:
> By the way, I think the old database is broken: I think it tries to install
> into some directory which now no longer exists. So I think the one in the
> newest beta is the only option.
In the same way (changed directories, changed import locati
> +1 for "SageMath Mathematics Software"
On the same subject: hadn't we agreed to change the "authors" field to
"The SageMath developers" ? The wiki page still shows a "William Stein
and others".
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-devel"
On 2015-09-11 17:26, John Cremona wrote:
"Sage Mathematics Software"
and not "SageMath " Should that change -- evn though "SageMath
Mathematics Software" sounds a little odd?
+1 for "SageMath Mathematics Software"
Daniel
--
You received this message because you are subscribed to the Goo
31 matches
Mail list logo
