Hi Francois and all,
On 1 Aug., 05:52, Francois Bissey
wrote:
> In the case of sage-marketing, no impact what so ever since I had no clue
> such a list existed.
QED...
> It is a
> bit of pity. sage-on-gentoo generates a bit of traffic on the gentoo-science
> mailing list and the occasional thre
On Mon, Aug 1, 2011 at 10:35 AM, Simon King wrote:
> Hi Francois and all,
>
> On 1 Aug., 05:52, Francois Bissey
> wrote:
>> In the case of sage-marketing, no impact what so ever since I had no clue
>> such a list existed.
>
> QED...
>
>> It is a
>> bit of pity. sage-on-gentoo generates a bit of t
Sometimes, it can happen that a patch only applies with "fuzz", for example:
$ hg import
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/11298/trac11298_singular_standard_options.rebase4.7.1.a1.patch
patching file doc/en/reference/misc.rst
Hunk #1 succeeded at 10 with fuzz 2 (offset 0 lin
On Monday, August 1, 2011 11:08:28 AM UTC+1, Jeroen Demeyer wrote:
>
> My personal opinion on applying patches with fuzz is that I allow
> patches with fuzz 1 but not with fuzz 2.
>
There is no guaranteed safe way of dealing with fuzzy patches. I think your
position is reasonable. Ideally, the pa
Hi John,
On 1 Aug., 11:48, John Cremona wrote:
> > That's why I think that the attitude of banning certain subjects and
> > interning them into specialised lists is dangerous for Sage.
>
> I have never thought that certain subjects should in any way be
> "banned" from sage-devel or sage-support.
Whenever I have suggested that a discussion move from sage-devel to
sage-algebra or sage-nt, it has not been because I did not want to see
it on sage-devel, but only because there are people who I thought
would be interested and have something useful to say on the topic who
would probably not see i
Hi!
On 1 Aug., 12:08, Jeroen Demeyer wrote:
> Sometimes, it can happen that a patch only applies with "fuzz", for example:
>
> $ hg
> importhttp://trac.sagemath.org/sage_trac/raw-attachment/ticket/11298/trac11...
> patching file doc/en/reference/misc.rst
> Hunk #1 succeeded at 10 with fuzz 2 (of
On 2011-07-29 22:44, kcrisman wrote:
> Right, but it would also seem that it is unwise to (say) try to add
> functionality on top of 4.7.1.rcx when tickets for overlapping code
> say "merged in 4.7.2.alphay". So, at least while Jeroen is release
> manager (which very happily seems to be an ongoing
To the sysadmin of the buildbot machine "cicero":
It seems that gcc and g++ have recently been upgraded to version 4.6.1
but gfortran is stuck at 4.6.0. Personally, I don't know what can go
wrong when mixing versions like this, but Sage doesn't like it:
checking if gcc accepts -dumpversion optio
On Mon, 01 Aug 2011 02:35:46 Simon King wrote:
> > It is a
> > bit of pity. sage-on-gentoo generates a bit of traffic on the
> > gentoo-science mailing list and the occasional thread here.
>
> sage-on-gentoo? Is that yet another list I haven't been aware of?
Just for clarification I work on portin
On Aug 1, 7:10 am, John Cremona wrote:
> Whenever I have suggested that a discussion move from sage-devel to
> sage-algebra or sage-nt, it has not been because I did not want to see
> it on sage-devel, but only because there are people who I thought
> would be interested and have something usefu
On Aug 1, 7:27 am, Jeroen Demeyer wrote:
> On 2011-07-29 22:44, kcrisman wrote:
>
> > Right, but it would also seem that it is unwise to (say) try to add
> > functionality on top of 4.7.1.rcx when tickets for overlapping code
> > say "merged in 4.7.2.alphay". So, at least while Jeroen is releas
Jeroen,
Everything looks ok. I have been able to successfully build
sage-4.7.1-rc0 using gcc-4.6.1 on cicero. Can you reproduce the
problem?
buildbot@cicero ~$ gfortran -v
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/local/gcc-4.6.1/x86-Linux-pentium4-fc/libexec/
gcc/i686
Hi!
On 1 Aug., 15:18, kcrisman wrote:
> sage-marketing, and probably others, were proposed because people on
> sage-devel didn't necessarily want to be bothered with tons of details
> of that nature.
sage-newbie, sage-solaris, sage-flame, sage-marketing and sage-edu
together made up for 133 post
On 8/1/11 3:08 AM, Jeroen Demeyer wrote:
Sometimes, it can happen that a patch only applies with "fuzz", for example:
$ hg import
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/11298/trac11298_singular_standard_options.rebase4.7.1.a1.patch
patching file doc/en/reference/misc.rst
Hunk #
On 8/1/11 7:19 AM, Simon King wrote:
sage-newbie, sage-solaris, sage-flame, sage-marketing and sage-edu
together made up for 133 posts in six months. Moving all of it to sage-
devel would mean an increment of about 4%. If part of it was moved to
sage-support instead, the increment would be even l
See #11551. Basically, we now more or less can (yet again) get Sage
to build on Cygwin, but in starting up there is a segfault caused by
Pari when creating a Pari float from an MPFR number
pari_float = cgetr(2 + rounded_prec / wordsize)
and cgetr is where the problem occurs.
I can get around th
> +1 for disbanding sage-marketing and merging that with sage-devel. +1
> for disbanding sage-newbie (encourage sage-support instead) and merging
> sage-solaris with sage-devel, and maybe even merging sage-windows with
> sage-devel.
Note that sage-newbie was never a support list, but instead an
On 7/31/11 2:55 PM, Rob Beezer wrote:
Kudos to Jason and the students at Drake. This is very nice.
Thanks! And thanks again for testing!
I've tried to "hide" some of the diagnostic information, and style a
few of the remaining elements. I've done this with my own crude CSS
stylesheet and
On 7/31/11 3:05 PM, Rob Beezer wrote:
On Jul 31, 2:55 pm, Rob Beezer wrote:
Some questions and observations.
Knew I was forgetting something.
8. Is there a way to "pre-load" the CodeMirror text area? Or more
precisely, what could I place into the HTML that would take some code
and load up
On 07/26/11 15:31, Burcin Erocal wrote:
>
> It is a good start. Here are some suggestions:
>
> - The code blocks should be preceeded with :: and indented. More
> information is available here:
>
> http://sagemath.org/doc/developer/conventions.html#documentation-strings
I don't see the "::" do
Hi Michael,
On 1 Aug., 18:53, Michael Orlitzky wrote:
> >http://sagemath.org/doc/developer/conventions.html#documentation-strings
>
> I don't see the "::" documented anywhere (did I read past it?). What do
> they do?
You are somehow right: Even though the :: is frequently used, it does
not seem
On Sun, Jul 31, 2011 at 12:37 AM, Jason Grout
wrote:
> On 7/29/11 5:11 PM, Jason Grout wrote:
>>
>> Hi everyone,
>>
>> I'd like to announce a trial beta run of a public single cell server:
>>
>> http://sagemath.org:5467/
>>
>> The idea is that this is a single cell that can very easily be embedded
sage: def foo(f):
for i in range(6000):
a = sage.calculus.calculus.symbolic_expression_from_string(f)
a=a.full_simplify()
return true
:
sage: foo("x*2+y^3+4")
--/
begin error---
On Monday, August 1, 2011 9:53:40 AM UTC-7, Michael Orlitzky wrote:
>
> On 07/26/11 15:31, Burcin Erocal wrote:
> >
> > It is a good start. Here are some suggestions:
> >
> > - The code blocks should be preceeded with :: and indented. More
> > information is available here:
> >
> > http://sa
http://fosspatents.blogspot.com/2011/04/red-hat-is-now-regular-customer-of.html
I usually keep out of GPL discussions but I came across this
discussion, which
it seems is talking about RedHat paying royalties (to patent trolls).
This may be more appropriate for sage-flames, but maybe not?
RJF
On Aug 1, 1:21 pm, "randomness...@hotmail.com"
wrote:
> sage: def foo(f):
> for i in range(6000):
> a = sage.calculus.calculus.symbolic_expression_from_string(f)
> a=a.full_simplify()
> return true
> :
>
> sage: foo("x*2+y^3+4")
>
>
> It does this error without the
Is this a known bug?
sage: a = RealField(200)(8.987551787368175506591796875e9)
sage: a
8.987551787368175506591796875000e9
sage: var('y')
y
sage: b = (a * x).mul(y, hold=True)
sage: b
(8.987551787368175506591796875000e9*x)*y
sage: c = (b / (x
On 8/1/11 10:21 AM, Ondřej Čertík wrote:
On Sun, Jul 31, 2011 at 12:37 AM, Jason Grout
wrote:
On 7/29/11 5:11 PM, Jason Grout wrote:
Hi everyone,
I'd like to announce a trial beta run of a public single cell server:
http://sagemath.org:5467/
The idea is that this is a single cell that can
Thank you for your response,
I am on sage 4.7 and I seem to get the error still with the timeit
line for easier readability (good suggestion). Do you mean that this
is a known bug in 4.7 and in 4.7.1 and later this seems to be fixed?
Or are you not getting this error in 4.7 either and maybe my dow
On 8/1/11 10:21 AM, Ondřej Čertík wrote:
Do you have some limit on the CPU time allowed
per evaluation?
The CPU time limit is for all user code evaluated in a single "session",
which for interacts may actually be multiple roundtrips to the server.
Jason
--
To post to this group, send an em
On Aug 1, 2011, at 11:43 , rjf wrote:
> This may be more appropriate for sage-flames,
+1
> but maybe not?
--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income
Experience is what you get
when you don't get what you want.
--
To p
On 7/30/11 7:58 PM, Kelvin Li wrote:
Sorry, I broke it again:
@interact
def f(a = input_grid(nrows=1, ncols=2, to_value=lambda t:3)):
pass
(throws an error that looks very similar to the previous one)
I think I've fixed it better now [1]. Can you check it again?
Thanks,
Jason
[1]
On Aug 1, 3:27 pm, "randomness...@hotmail.com"
wrote:
> Thank you for your response,
>
> I am on sage 4.7 and I seem to get the error still with the timeit
> line for easier readability (good suggestion). Do you mean that this
> is a known bug in 4.7 and in 4.7.1 and later this seems to be fixed
On Aug 1, 3:17 pm, Eviatar wrote:
> Is this a known bug?
Perhaps it is better to say that it is a confusing feature.
sage: x.simplify?
Note: Currently, this just sends the expression to Maxima and
converts
it back to Sage.
In particular, the precision will not be carried ove
On 1 Aug., 21:41, "Justin C. Walker" wrote:
> On Aug 1, 2011, at 11:43 , rjf wrote:
>
> > This may be more appropriate for sage-flames,
>
> +1
-1
> > but maybe not?
+1
As I have pointed out in another thread, I am against having an
abundance of small lists. I am not a lawier, but it seems to m
On 7/31/11 3:05 PM, Rob Beezer wrote:
8. Is there a way to "pre-load" the CodeMirror text area? Or more
precisely, what could I place into the HTML that would take some code
and load up the text area with the code as its content? Maybe this
should be an argument to the singlecell creation func
On Aug 1, 2011, at 13:27 , Simon King wrote:
> On 1 Aug., 21:41, "Justin C. Walker" wrote:
>> On Aug 1, 2011, at 11:43 , rjf wrote:
>>
>>> This may be more appropriate for sage-flames,
>>
>> +1
>
> -1
>
>>> but maybe not?
>
> +1
While I agree with you on the subject of list proliferation,
On 8/1/11 1:30 PM, Jason Grout wrote:
On 7/31/11 3:05 PM, Rob Beezer wrote:
8. Is there a way to "pre-load" the CodeMirror text area? Or more
precisely, what could I place into the HTML that would take some code
and load up the text area with the code as its content? Maybe this
should be an argu
Oh, I just assumed the interface with Maxima would maintain precision.
On Aug 1, 1:03 pm, kcrisman wrote:
> On Aug 1, 3:17 pm, Eviatar wrote:
>
> > Is this a known bug?
>
> Perhaps it is better to say that it is a confusing feature.
>
> sage: x.simplify?
>
> Note: Currently, this just se
On Monday, August 1, 2011 4:12:12 PM UTC+1, jason wrote:
>
> Pardon my ignorance, but what does "fuzz n" mean and how is it different
> for different values of n?
>
Let me quote "man patch":
With context diffs, and to a lesser extent with normal diffs,
patch can
detect when
As far as I can tell, these two scripts are the same, except sage-open
is better, and is apparently the only one used in the Sage library.
So, should we get rid of sage-osx-open? Not that it's hurting
anybody...
- kcrisman
--
To post to this group, send an email to sage-devel@googlegroups.com
On Sun, Jul 31, 2011 at 11:51 PM, Francois Bissey
wrote:
> I'll give it a spin as soon as it is available for gentoo and report the
> problems in this thread. How does that sound?
Sounds great, modulo one key detail: let's have the discussion on the
ipython-dev list (http://mail.scipy.org/mailman
On Aug 1, 8:50 am, Jason Grout wrote:
> Can you post your current working/nonworking version so I can test it too?
Thanks, Jason, for all the details. I'll try to put up an example or
two, incorporating what you have suggested.
Right now, it looks like something has changed and is not working f
On Aug 1, 1:42 pm, Eviatar wrote:
> Oh, I just assumed the interface with Maxima would maintain precision.
It could. Maxima does have a notion of multiprecision floats. They are
base 2, so interfacing with MPFR should be a cinch. Especially with
lib_maxima, translating MPFR to maxima multiprec an
> On Sun, Jul 31, 2011 at 11:51 PM, Francois Bissey
>
> wrote:
> > I'll give it a spin as soon as it is available for gentoo and report the
> > problems in this thread. How does that sound?
>
> Sounds great, modulo one key detail: let's have the discussion on the
> ipython-dev list (http://mail.
On 8/1/11 4:23 PM, Rob Beezer wrote:
On Aug 1, 8:50 am, Jason Grout wrote:
Can you post your current working/nonworking version so I can test it too?
Thanks, Jason, for all the details. I'll try to put up an example or
two, incorporating what you have suggested.
Right now, it looks like som
On 8/1/11 4:37 PM, Jason Grout wrote:
On 8/1/11 4:23 PM, Rob Beezer wrote:
On Aug 1, 8:50 am, Jason Grout wrote:
Can you post your current working/nonworking version so I can test it
too?
Thanks, Jason, for all the details. I'll try to put up an example or
two, incorporating what you have sug
On 8/1/11 4:23 PM, Rob Beezer wrote:
On Aug 1, 8:50 am, Jason Grout wrote:
Can you post your current working/nonworking version so I can test it too?
Thanks, Jason, for all the details. I'll try to put up an example or
two, incorporating what you have suggested.
Right now, it looks like som
On 8/1/11 5:07 PM, Jason Grout wrote:
I should just mention that the above line is for ipad/android tablet
devices. It makes a world of difference in how small the things on the
screen are and how usable everything is on the tablets/iphones. We
should maybe look into using it for the sage
On Mon, Aug 1, 2011 at 6:28 PM, Francois Bissey
wrote:
>
> I have now subscribed to IPython-dev. I will start a thread when things
> starts happening. I will start by updating sympy in sage to 0.7.1 as they
> have taken care of compatibility problems with IPython-0.11 already.
> It may be that oth
On Aug 1, 5:07 pm, Jason Grout wrote:
> Ah, I didn't realize you meant that I broke the normal singlecell
> because I forgot that I changed things ;). It's working now.
Thanks, Jason, for the quick fixes and ideas.
Working demo at:
http://buzzard.ups.edu/misc/singlecell/singlecell-minimal.html
On 8/1/11 5:52 PM, Rob Beezer wrote:
On Aug 1, 5:07 pm, Jason Grout wrote:
Ah, I didn't realize you meant that I broke the normal singlecell
because I forgot that I changed things ;). It's working now.
Thanks, Jason, for the quick fixes and ideas.
Working demo at:
http://buzzard.ups.edu/mi
This is now #11643, http://trac.sagemath.org/sage_trac/ticket/11643.
On Aug 1, 4:25 pm, Nils Bruin wrote:
> On Aug 1, 1:42 pm, Eviatar wrote:
>
> > Oh, I just assumed the interface with Maxima would maintain precision.
>
> It could. Maxima does have a notion of multiprecision floats. They are
>
OK, demo updated and everything seems to be working as intended now.
http://buzzard.ups.edu/misc/singlecell/singlecell-minimal.html
> Tab completion seems a bit...interesting to do
Right. I guess the most we could hope for would be completion on
global stuff - functional syntax like log() and
On 8/1/11 7:31 PM, Rob Beezer wrote:
OK, demo updated and everything seems to be working as intended now.
http://buzzard.ups.edu/misc/singlecell/singlecell-minimal.html
I changed the public API (which probably broke your demo). Here is a
new example. Note that now it's easy to change the te
On Aug 1, 11:21 am, "randomness...@hotmail.com"
wrote:
> sage: def foo(f):
> for i in range(6000):
> a = sage.calculus.calculus.symbolic_expression_from_string(f)
> a=a.full_simplify()
> return true
> :
>
> sage: foo("x*2+y^3+4")
>
>
On Aug 1, 10:02 pm, Jason Grout wrote:
> I changed the public API (which probably broke your demo).
Still working, it seems. I don't think you changed anything I'm
using.
> But it does let you seamlessly embed interacts in webpages
> with just a simple button to make the interact live.
That'
58 matches
Mail list logo
