วันอาทิตย์ที่ 31 กรกฎาคม พ.ศ. 2554

Re: [sage-devel] Re: Spam from sage-devel

I got it too. It was correctly catched by the university mail filter but left
me puzzled too.

Francois

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: Re: [sage-devel] Re: Fwd: [IPython-dev] [ANN] IPython 0.11 is officially out

On Sun, 31 Jul 2011 23:21:30 Fernando Perez wrote:
> On Sun, Jul 31, 2011 at 10:59 PM, François
>
> <francois.bissey@canterbury.ac.nz> wrote:
> > For those interested Jason Grout has already filled a ticket to upgrade
> > to ipython-0.10.2 (trac #11460) with a comment that Fernando told him
> > that it would be better to skip 0.11.
>
> I should qualify that comment with a bit of context: there's a TON of
> changes in 0.11, and the internal customization APIs are all very
> different. This means a lot of stuff that Sage does won't work out of
> the box with 0.11.
>
> However, we will need some help from the Sage team to find out areas
> where we may have inadvertently dropped a feature or removed an entry
> point without putting in a replacement in the new APIs. Since Sage
> makes more intense use of IPython than most other projects, there are
> things we'll only find out about once Sage tries to update.
>
> All this means that while 0.11 is not likely to be an easy update for
> Sage, simply waiting will not work either. The best approach would be
> for someone to give 0.11 a try and let us know what breaks by opening
> issues in our tracker (https://github.com/ipython/ipython/issues) and
> asking on our -dev mailing list
> (http://mail.scipy.org/mailman/listinfo/ipython-dev). That way,
> hopefully they will get resolved during the 0.12 cycle and then when
> 0.12 does come out, it will be realistic for Sage to actually upgrade
> without troubles.
>
Hi,

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?

Francois

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Fwd: [IPython-dev] [ANN] IPython 0.11 is officially out

On Sun, Jul 31, 2011 at 10:59 PM, François
<francois.bissey@canterbury.ac.nz> wrote:
> For those interested Jason Grout has already filled a ticket to upgrade to
> ipython-0.10.2 (trac #11460) with a comment that Fernando told him that
> it would be better to skip 0.11.

I should qualify that comment with a bit of context: there's a TON of
changes in 0.11, and the internal customization APIs are all very
different. This means a lot of stuff that Sage does won't work out of
the box with 0.11.

However, we will need some help from the Sage team to find out areas
where we may have inadvertently dropped a feature or removed an entry
point without putting in a replacement in the new APIs. Since Sage
makes more intense use of IPython than most other projects, there are
things we'll only find out about once Sage tries to update.

All this means that while 0.11 is not likely to be an easy update for
Sage, simply waiting will not work either. The best approach would be
for someone to give 0.11 a try and let us know what breaks by opening
issues in our tracker (https://github.com/ipython/ipython/issues) and
asking on our -dev mailing list
(http://mail.scipy.org/mailman/listinfo/ipython-dev). That way,
hopefully they will get resolved during the 0.12 cycle and then when
0.12 does come out, it will be realistic for Sage to actually upgrade
without troubles.

Cheers,

f

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Spam from sage-devel

Hmmm... I see it says "sage-devel@googlegroups.com via madmimi.com",
so maybe you're right. "This means that the sender may be using a
third-party email service to generate this message", according to the
Gmail help website.

On Jul 31, 9:13 pm, David Joyner <wdjoy...@gmail.com> wrote:
> Yes, I think they forged the email From address, but I'm not sure.
> It did not seem to actually come from googlegroups.
>
>
>
>
>
>
>
> On Mon, Aug 1, 2011 at 12:10 AM, Eviatar <eviatarb...@gmail.com> wrote:
> > Hello,
>
> > I just got the following email from the address sage-
> > devel@googlegroups.com:
>
> > Want to become a SAP expert?
> > Want to have a Certificate of SAP?
> > SAP Consultan Earn More Than $1000/Day...
>
> > Dear SAPer,
> > Why you should choose a career in SAP? You might already know that it
> > is one of the best and highest paying job you'll ever find. Here's
> > why:
>
> >    There are now 44.500 installations of SAP, in 120 countries, with
> > more then 10 million users
> >    Top companies in any countries with the highest market value use
> > SAP software. This means you will be marketable and in-demand among
> > the any large firms.
> >    You could earn more than $1000/Day as a SAP professional.
> >    SAP AG is investing over $5 billion in the next 5 years. Wow...
> > that's "Billion"
>
> > Did this happen to anyone else?
>
> > --
> > To post to this group, send an email to sage-devel@googlegroups.com
> > To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
> > For more options, visit this group athttp://groups.google.com/group/sage-devel
> > URL:http://www.sagemath.org

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Spam from sage-devel

Yes, I think they forged the email From address, but I'm not sure.
It did not seem to actually come from googlegroups.


On Mon, Aug 1, 2011 at 12:10 AM, Eviatar <eviatarbach@gmail.com> wrote:
> Hello,
>
> I just got the following email from the address sage-
> devel@googlegroups.com:
>
> Want to become a SAP expert?
> Want to have a Certificate of SAP?
> SAP Consultan Earn More Than $1000/Day...
>
> Dear SAPer,
> Why you should choose a career in SAP? You might already know that it
> is one of the best and highest paying job you'll ever find. Here's
> why:
>
>    There are now 44.500 installations of SAP, in 120 countries, with
> more then 10 million users
>    Top companies in any countries with the highest market value use
> SAP software. This means you will be marketable and in-demand among
> the any large firms.
>    You could earn more than $1000/Day as a SAP professional.
>    SAP AG is investing over $5 billion in the next 5 years. Wow...
> that's "Billion"
>
> Did this happen to anyone else?
>
> --
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Spam from sage-devel

Hello,

I just got the following email from the address sage-
devel@googlegroups.com:

Want to become a SAP expert?
Want to have a Certificate of SAP?
SAP Consultan Earn More Than $1000/Day...

Dear SAPer,
Why you should choose a career in SAP? You might already know that it
is one of the best and highest paying job you'll ever find. Here's
why:

There are now 44.500 installations of SAP, in 120 countries, with
more then 10 million users
Top companies in any countries with the highest market value use
SAP software. This means you will be marketable and in-demand among
the any large firms.
You could earn more than $1000/Day as a SAP professional.
SAP AG is investing over $5 billion in the next 5 years. Wow...
that's "Billion"

Did this happen to anyone else?

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Fwd: [IPython-dev] [ANN] IPython 0.11 is officially out

For those interested Jason Grout has already filled a ticket to upgrade to
ipython-0.10.2 (trac #11460) with a comment that Fernando told him that
it would be better to skip 0.11.

There is a new spkg on that ticket that needs testing, especially on OS X
and with sage -gdb.

Francois

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: List condensation

> Hi Francois,
>
> On 31 Jul., 23:48, Francois Bissey <francois.bis...@canterbury.ac.nz>
>
> wrote:
> > You forgot debian-sage
>
> Indeed. Sorry.
>
> Actually I attempted completeness; I did some searches, but debian-
> sage has not been found. It is another list that had no activity since
> Oct. 05, 2010.
>
> I hope you allow a direct question: Did you have the impression that
> the existence of a small list (just 40 members, sage-marketing has
> even less) dedicated to a particular project (packaging Sage) helped
> to increase the intensity of work on that project, since it made it
> more easy to focus? Or did it decrease intensity, since there has only
> been little feed-back from the swarm?
>

In the case of sage-marketing, no impact what so ever since I had no clue
such a list existed.

> How many people are aware of debian-sage (or further lists that I may
> have forgotten as well)? Is my fear justified that progress on a
> project is lost, if information on that progress is buried in an
> almost forgotten list?
>

Not many, according to William it was misnamed as well since we ended
up working accross linux distributions. There are not many people packaging
for linux distro. There was Tim Abbott for debian for a while, me and three
other core members work (semi-)regularly on sage-on-gentoo. Paulo Cesar de
Andrade maintains sage on Mandriva. There may be others I am not aware
off. I discussed the matter of a separate mailing list with Paulo but there
wouldn't be enough traffic. I have irregular communications with Paulo. 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.

You could say I mostly work beyond the scene on sage-devel by pushing
my distro's agenda :) .

I guess there are a number of emails that I had with Burcin about sage-prefix
and some other members of sage-on-gentoo that would be material for sage-devel
but some people may object us discusing it here. Plus some of these people
actually favor private email. You could say that's an even worst scenario than
being buried on an obscure mailing list.

Francois

[sage-devel] Re: List condensation

Hi Francois,

On 31 Jul., 23:48, Francois Bissey <francois.bis...@canterbury.ac.nz>
wrote:
> You forgot debian-sage

Indeed. Sorry.

Actually I attempted completeness; I did some searches, but debian-
sage has not been found. It is another list that had no activity since
Oct. 05, 2010.

I hope you allow a direct question: Did you have the impression that
the existence of a small list (just 40 members, sage-marketing has
even less) dedicated to a particular project (packaging Sage) helped
to increase the intensity of work on that project, since it made it
more easy to focus? Or did it decrease intensity, since there has only
been little feed-back from the swarm?

How many people are aware of debian-sage (or further lists that I may
have forgotten as well)? Is my fear justified that progress on a
project is lost, if information on that progress is buried in an
almost forgotten list?

Best regards,
Simon

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

On Jul 31, 2:55 pm, Rob Beezer <goo...@beezer.cotse.net> 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 the text area with the code as its content? Maybe this
should be an argument to the singlecell creation function?

Incidentally increasing list traffic,
Rob

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

Kudos to Jason and the students at Drake. This is very nice.

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 via the arguments to the singlecell creation function.
Some questions and observations.

1. Starting from the current HTML page being served from
sagemath.org, where would one add the reference to a "custom" CSS
file? I have this mostly working right, but probably not correctly.
In particular, setting many of the output parts to not display has
totally broken interacts, so in that sense what I have done is
definitely not correct.

2. Using arguments to the singlecell creation function to turn-off
the messages (three values set to false) seems to also break
interacts.

3. The default value of "outputDiv" listed in the documentation for
the dictionary of options to the single cell creation caused an error
for me, but a value of "#singlecell" does seem to work.

4. Maybe the singlecell_completion div can be not-displayed when
"messages" is false?

5. I was able to put two apparently independent single-cells on the
same page by running singlecell.makeSinglecell(alternate_config)
where alternate_config specified a different id for a second div
used to locate the cell. Maybe not news, but I did not see this
documented anywhere. In particular I was just guessing about how to
properly invoke the singlecell creation function.

6. Minor nit: CodeMirror does not handle the "F.<a> = GF(3^2)"
syntax properly.

7. Do interacts time-out after some period of inactivity? It seems
so.

Rob

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] List condensation

> Hi!
>
> I don't know how to measure the activity on ask-sage. Here is a
> summary of the frequency of posts on the different sage google groops
> over the past few months, listing the number of posts per month and
> the total number from February to July. I ordered the lists by
> increasing activity:
>
>  sage-newbie: None since June 2, 2008. Total 0
>  sage-solaris: None since Nov. 25, 2010.  Total 0
> sage-flame: 4, 0, 13, 0, 0, 0.                   Total: 17
> sage-marketing: 5, 0, 1, 0, 4, 11.            Total: 21
> sage-algebra: 4, 56, 3, 17, 4, 2.              Total: 86
>      sage-edu: 4, 32, 24, 10, 11, 14.         Total: 95
> sage-windows: 6, 5, 46, 6, 20, 24.           Total: 107
>         sage-nt: 21, 10, 16, 7, 49, 12.         Total: 115
> sage-release: 84, 61, 119, 152, 64, 70.    Total: 550
> sage-combinat-devel: 154,292,135,129,108,77. Total: 895
> sage-support: 291, 326, 302, 291, 269, 263. Total: 1742
> sage-devel: 654, 581,699, 607, 421, 435.  Total: 3397
>
You forgot debian-sage, since Tim Abbot has left us not
much is happening over there has a lot of what was going was
driven by him and me.

Francois

[sage-devel] Fwd: [IPython-dev] [ANN] IPython 0.11 is officially out

---------- Forwarded message ----------
From: Fernando Perez <fperez.net@gmail.com>
Date: Sun, Jul 31, 2011 at 10:19 AM
Subject: [IPython-dev] [ANN] IPython 0.11 is officially out
To: IPython Development list <ipython-dev@scipy.org>, IPython User
list <ipython-user@scipy.org>, Discussion of Numerical Python
<numpy-discussion@scipy.org>, SciPy Developers List
<scipy-dev@scipy.org>, SciPy Users List <scipy-user@scipy.org>,
Matplotlib Users <matplotlib-users@lists.sourceforge.net>, NIPY
Developer's List <nipy-devel@neuroimaging.scipy.org>


Hi all,

on behalf of the IPython development team, I'm thrilled to announce,
after more than two years of development work, the official release of
IPython 0.11.

This release brings a long list of improvements and new features
(along with hopefully few new bugs).  We have completely refactored
IPython, making it a much more friendly project to participate in by
having better separated and organized internals.  We hope you will not
only use the new tools and libraries, but also join us with new ideas
and development.

After this very long development effort, we hope to make a few
stabilization releases at a quicker pace, where we iron out the kinks
in the new APIs and complete some remaining internal cleanup work.  We
will then make a (long awaited) IPython 1.0 release with these stable
APIs.

*Downloads*
Download links and instructions are at: http://ipython.org/download.html
And IPython is also on PyPI: http://pypi.python.org/pypi/ipython

Those contain a built version of the HTML docs; if you want pure
source downloads with no docs, those are available on github:

Tarball: https://github.com/ipython/ipython/tarball/rel-0.11
Zipball: https://github.com/ipython/ipython/zipball/rel-0.11

* Features *
Here is a quick listing of the major new features:

- Standalone Qt console
- High-level parallel computing with ZeroMQ
- New model for GUI/plotting support in the terminal
- A two-process architecture
- Fully refactored internal project structure
- Vim integration
- Integration into Microsoft Visual Studio
- Improved unicode support
- Python 3 support
- New profile model
- SQLite storage for history
- New configuration system
- Pasting of code with prompts

And many more...

We closed over 500 tickets, merged over 200 pull requests, and more
than 60 people contributed over 2200 commits for the final release.
Please see our release notes for the full details on everything about
this release: https://github.com/ipython/ipython/zipball/rel-0.11

As usual, if you find any problem, please file a ticket --or even
better, a pull request fixing it-- on our github issues site
(https://github.com/ipython/ipython/issues/).

Many thanks to all who contributed!

Fernando, on behalf of the IPython development team.

http://ipython.org
_______________________________________________
IPython-dev mailing list
IPython-dev@scipy.org
http://mail.scipy.org/mailman/listinfo/ipython-dev

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] List condensation

Hi!

I don't know how to measure the activity on ask-sage. Here is a
summary of the frequency of posts on the different sage google groops
over the past few months, listing the number of posts per month and
the total number from February to July. I ordered the lists by
increasing activity:

sage-newbie: None since June 2, 2008. Total 0
sage-solaris: None since Nov. 25, 2010. Total 0
sage-flame: 4, 0, 13, 0, 0, 0. Total: 17
sage-marketing: 5, 0, 1, 0, 4, 11. Total: 21
sage-algebra: 4, 56, 3, 17, 4, 2. Total: 86
sage-edu: 4, 32, 24, 10, 11, 14. Total: 95
sage-windows: 6, 5, 46, 6, 20, 24. Total: 107
sage-nt: 21, 10, 16, 7, 49, 12. Total: 115
sage-release: 84, 61, 119, 152, 64, 70. Total: 550
sage-combinat-devel: 154,292,135,129,108,77. Total: 895
sage-support: 291, 326, 302, 291, 269, 263. Total: 1742
sage-devel: 654, 581,699, 607, 421, 435. Total: 3397

I mainly wonder about the lists of medium size.

It seems to me that there is a broad thematic overlap between sage-
algebra, sage-nt and sage-combinat-devel. For example, if I have a
question on categories and coercion, then I am always uncertain
whether I should better post on sage-algebra or sage-combinat-devel.
Once, I had a question on coercion of number fields, and the
discussion has eventually been moved to sage-nt.

So, first question: Couldn't these three lists be combined into one?
Sorry that I can not suggest a good name for a combined list. They are
all about "abstract nonsense", but that's perhaps not a good name...

Second question: Why is the development of Sage on Windows and Solaris
not discussed in front of a larger audience, namely on sage-devel?

It is often stated that a native Windows port is one of the most
important short (or mid?) term goals of Sage. I think that moving sage-
windows and sage-solaris to sage-devel, which is read by more people,
would underline its importance. I think it can hardly be called a
problem if the number of posts on sage-devel would increase by
107/3397, which is less than 3.5%.

Thirdly, I wonder whether sage-edu and sage-marketing couldn't be
covered by sage-devel and sage-support as well.

I acknowledge that there have been reasons to create the small lists.
Also, it is a valid approach to have a separate list for the main
thematic areas of Sage. But then, why is there no list for symbolics
(or is there?)?

Moreover, reasons can change over time. I think that one reasonably
large list is more easy to follow than three small ones. And I expect
that having fewer but bigger lists would foster productivity. And if
one is really not interested in, say, the Windows port, then I think
it is quite easy to skip reading a post after seeing the subject line.

But I have no experience in project management, and more experienced
people may disagree with my expectation?

Best regards,
Simon

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: [sage-notebook] Re: public single cell server

Yep, it seems they work now. Great!

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: [sage-notebook] Re: public single cell server

On 7/30/11 2:40 AM, Juanlu001 wrote:
> I have tested multiple interacts of mine and some computations, and
> everything seems to work quite well except for the backslash \, which I
> tried to use to split lines. It gives a syntax error:
>
> SyntaxError Traceback (most recent call last)
> SyntaxError: invalid syntax (<string>, line 57)


Backslashes should work now. Can you test it please?

Thanks,

Jason

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

วันเสาร์ที่ 30 กรกฎาคม พ.ศ. 2554

[sage-devel] Re: public single cell server

On 7/30/11 10:30 PM, John Travis wrote:
> Great. I'm having to look harder for problems so that's good. Check
> out the spacing issue on the label rho(x,y,z) for
>
> @interact(layout=dict(top=[['rho','a1']]))
> def _(
> a1 = input_box(2,label='$a_1$'),
> rho=input_box(x,label='$\\rho(x,y,z)$',width=8)):
> print "hello"


What do you see as the problem with the output? I can see that the two
textboxes are a little close together (i.e., the $a_1$ is too close to
the end of the $\rho$ textbox). Is that what you mean?

Thanks,

Jason

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

On 7/30/11 7:58 PM, Kelvin Li wrote:
> On Jul 30, 5:25 pm, Jason Grout<jason-s...@creativetrax.com> wrote:
>
>> Soon I will make it so that you can just have a non-colored plain text
>> box, or toggle between the fancy and non-fancy editors.
>
> That would be cool!
>
>>> For interacts, looks like "input_grid" and "color_selector" widgets
>>> have problems. To reproduce:
>>
>>> @interact
>>> def f(a = input_grid(nrows=0, ncols=0)):
>>> pass
>>
>>> (throws a syntax error about an internal file)
>>
>> This is now fixed. Can you test it please?
>
> 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)

Yep, it should be the same error. Okay, I will have to fix this a
little more robustly. I think I know what to do. This is tracked here:
https://github.com/jasongrout/simple-python-db-compute/issues/179

>
> Here are some more things I found (which might already be known
> issues):
>
> -- The "function?" help notation does not work. Using "help(function)"
> returns raw HTML code in the cell along with an attached file that
> does contain the docstring of "function".
>
> -- Entering "graph_editor()" returns the text "Not Found / The
> requested URL was not found on the server. / If you entered the URL
> manually please check your spelling and try again" and the "save" and
> "close" buttons of the non-functioning graph editor.

Both of these are known issues and not considered show-stoppers for now.
Thanks for reporting these. The graph editor depends heavily on
hacking and kludges dealing with the current notebook, so it will need
to have some major changes to work. One reason I didn't pay too much
attention to the graph editor or the help is that these single-cell
instances are concentrating on a single execution and result. The graph
editor just builds a graph, but then you wouldn't be able to do anything
with it. Likewise, the help will return something, but then you'll need
to execute something again in order to do something with it. Both of
those sorts of computations lend themselves more towards a notebook with
multiple cells, rather than a single-cell system.

That said, we'll eventually get this working, since hopefully we can use
code and what we've learned here to make the current notebook better.

Thanks,

Jason

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

Great. I'm having to look harder for problems so that's good. Check
out the spacing issue on the label rho(x,y,z) for

@interact(layout=dict(top=[['rho','a1']]))
def _(
a1 = input_box(2,label='$a_1$'),
rho=input_box(x,label='$\\rho(x,y,z)$',width=8)):
print "hello"

JT

On Jul 30, 4:09 pm, Jason Grout <jason-s...@creativetrax.com> wrote:
> On 7/30/11 7:57 AM, John Travis wrote:
>
> > A real minor problem I found was with labels in interact.  No latex
> > for such as
>
> > def _(  x0 = input_box(0,width=5,label='$x_0$'), blah
>
> This is fixed now; if you have time, please test it.
>
> Thanks,
>
> Jason

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

On Jul 30, 5:25 pm, Jason Grout <jason-s...@creativetrax.com> wrote:

> Soon I will make it so that you can just have a non-colored plain text
> box, or toggle between the fancy and non-fancy editors.

That would be cool!

> > For interacts, looks like "input_grid" and "color_selector" widgets
> > have problems. To reproduce:
>
> > @interact
> > def f(a = input_grid(nrows=0, ncols=0)):
> >      pass
>
> > (throws a syntax error about an internal file)
>
> This is now fixed.  Can you test it please?

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)

> > @interact
> > def f(a = color_selector()):
> >      print a
>
> > (widget mis-renders in my browser. I took screenshots, but I don't
> > know where to upload the images.)
>
> This is now fixed.  Can you test it please?

Passes my (very simple) tests!

> > Note that all of the above results were correct as of last night. For
> > some reason, none of the interacts or plots is working for me this
> > morning.
>
> That's interesting that they worked last night---they shouldn't have.
> Maybe you had some things loaded in cache from a while ago, but your
> cache has been cleared since then...

If I recall correctly, I tested it around 22:00 to 00:00 Pacific Time,
and that was my first time using the single cell server. Would there
be things left over in the cache? And for some magical reason, what
seemed broken this morning all works again this afternoon. :-)

Here are some more things I found (which might already be known
issues):

-- The "function?" help notation does not work. Using "help(function)"
returns raw HTML code in the cell along with an attached file that
does contain the docstring of "function".

-- Entering "graph_editor()" returns the text "Not Found / The
requested URL was not found on the server. / If you entered the URL
manually please check your spelling and try again" and the "save" and
"close" buttons of the non-functioning graph editor.

Kelvin

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

On 7/30/11 12:01 PM, Kelvin Li wrote:
> Wow, this is really neat!
>
> Out of laziness/incompetence to do any deeper investigation, I will
> list my complaints in no particular order. :-)
>
> The syntax highlighting is really cool, but when there is a lot of
> text, scrolling through it with the arrow keys can be slow/jerky (at
> least in my browser: Firefox 5.0 on Linux).
>

Soon I will make it so that you can just have a non-colored plain text
box, or toggle between the fancy and non-fancy editors.

> It looks like the 3D plotters "jmol" and "tachyon" work (but I don't
> have a java plugin to know for sure), but "canvas3d" does not. It
> gives me a link to a file that I can download (??). It works on
> sagenb.org -- which hopefully rules out my browser as the issue.

This is now being tracked at
https://github.com/jasongrout/simple-python-db-compute/issues/178.

>
> For interacts, looks like "input_grid" and "color_selector" widgets
> have problems. To reproduce:
>
> @interact
> def f(a = input_grid(nrows=0, ncols=0)):
> pass
>
> (throws a syntax error about an internal file)

This is now fixed. Can you test it please?

>
> @interact
> def f(a = color_selector()):
> print a
>
> (widget mis-renders in my browser. I took screenshots, but I don't
> know where to upload the images.)

This is now fixed. Can you test it please?


>
> The other interact widgets I tested all work.

Great!

>
> Note that all of the above results were correct as of last night. For
> some reason, none of the interacts or plots is working for me this
> morning.


That's interesting that they worked last night---they shouldn't have.
Maybe you had some things loaded in cache from a while ago, but your
cache has been cleared since then...


>
> Anyways, that was my attempt at hammering it. :-)

Thanks!

Jason

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Can please someone do a little test on t2 or mark?

On Sat, Jul 30, 2011 at 12:01 PM, Simon King <simon.king@uni-jena.de> wrote:
> Hi!
>
> The following is a problem that was observed with trac ticket #11431
> on the build bots mark and t2: The line
>    singular.eval('ring r1 = (9,x),(a,b,c,d,e,f),
> (M((1,2,3,0)),wp(2,3),lp)')
> fails with the patch from the ticket.
>
> However, the ticket does not change how a string is interpreted/
> executed in Singular - it only affects how stuff in Singular (such as
> lists, ideals and strings) is translated into the corresponding object
> in Sage.
>
> So, I wonder whether the failure was caused by the patch, or whether
> it just accidentally revealed an existing bug by a new doc test.
>
> I currently have no new Sage version on my t2 account. Can please one
> of you with a recent Sage version test it on t2 or mark?
>
> It would also help if someone could remind me how to build Sage on t2
> on my own. Then, I could test it myself...

Unfortunately, t2 is currently toast, due to the fileserver dying.


- William

>
> Best regards,
> Simon
>
> --
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>

--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

On 7/30/11 7:57 AM, John Travis wrote:
> A real minor problem I found was with labels in interact. No latex
> for such as
>
> def _( x0 = input_box(0,width=5,label='$x_0$'), blah

This is fixed now; if you have time, please test it.

Thanks,

Jason


--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: 4.7.2.alpha0?

On Sat, 30 Jul 2011 02:31:33 leif wrote:
> On 29 Jul., 23:37, Francois Bissey <francois.bis...@canterbury.ac.nz>
>
> wrote:
> > On Fri, 29 Jul 2011 13:44:01 kcrisman wrote:
> > > So it would be helpful to have some clarification, if only to avoid
> > > rebasing.
> >
> > What I did last time I had a problem like that was to make my ticket
> > dependent of the ticket already in the unofficial release. That way
> > there is an explicit dependency chain.
>
> Of course, but not really a solution.
>
> What happens if the patch(es) / ticket(s) you based your changes on
> get unmerged again for some reason? The same as if you hadn't based
> your ticket on the "candidate(s)" but these stay in.
> And people wanting to try / review your ticket (patchbot included)
> also need to apply the whole, perhaps "artificially grown" dependency
> chain. Things get worse with spkgs that require rebuilding others or
> applying some patches in addition.
>
> There's no stays-merged probability field for the tickets on the
> list... ;-)
> (And trying to judge that from the "candidate" tickets is more work,
> if at all possible, since further tickets you probably didn't think of
> because they weren't listed might break them at any time.)
>
>
> I actually ran into the situation having to rebase a patch of an
> already (quite long) positively reviewed ticket on a new patch merged
> into devel release N+2 (N: current official devel version).
>
> I provided an alternate patch for that version, and in fact the ticket
> I rebased the patch to still remained in version N+2 when it was
> officially announced quite a while later, but my ticket now again
> needs review, thereby delaying another positively reviewed one which
> depends on the former. [Maybe it would have gotten re-reviewed if I
> attached the rebased patch earlier, but who wants to test against an
> unofficial release with in general arbitrary dependencies?]
>
>
> IMHO the more or less volatile (nobody knows) unofficial releases
> cause more confusion, at least if one follows Francois' suggestion and
> "ignores" what the README.FIRSTs state:
>
> "[...] There is no point in testing it. [...]"
>
> "That being said, it can still be useful to use a non-released Sage
> version for rebasing a patch, but don't complain if the version
> changed and broke your patch. [...]" (The older ones didn't say that
> IIRC.)
>
> A few people will base their patches on the current devel, others on
> some uncertain, sometimes frequently changing future release.
>
> Things would be a little easier if trac supported different branches,
> though it wouldn't be clear whether some dependencies are of
> functional or just "syntactical" nature.
>
>
Of course there is always a risk. Providing an alternate patch based on the
current official release is a must. Also you should be able to assess
the probability that the patch set in the unreleased will stay merged.
If the change is trivial you should be safe.

You probably also should do a review of the dependency you depend
on for yourself. None of that will prevent unmerging if a major concern
arises.

Francois

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Can please someone do a little test on t2 or mark?

Hi!

The following is a problem that was observed with trac ticket #11431
on the build bots mark and t2: The line
singular.eval('ring r1 = (9,x),(a,b,c,d,e,f),
(M((1,2,3,0)),wp(2,3),lp)')
fails with the patch from the ticket.

However, the ticket does not change how a string is interpreted/
executed in Singular - it only affects how stuff in Singular (such as
lists, ideals and strings) is translated into the corresponding object
in Sage.

So, I wonder whether the failure was caused by the patch, or whether
it just accidentally revealed an existing bug by a new doc test.

I currently have no new Sage version on my t2 account. Can please one
of you with a recent Sage version test it on t2 or mark?

It would also help if someone could remind me how to build Sage on t2
on my own. Then, I could test it myself...

Best regards,
Simon

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

Wow, this is really neat!

Out of laziness/incompetence to do any deeper investigation, I will
list my complaints in no particular order. :-)

The syntax highlighting is really cool, but when there is a lot of
text, scrolling through it with the arrow keys can be slow/jerky (at
least in my browser: Firefox 5.0 on Linux).

It looks like the 3D plotters "jmol" and "tachyon" work (but I don't
have a java plugin to know for sure), but "canvas3d" does not. It
gives me a link to a file that I can download (??). It works on
sagenb.org -- which hopefully rules out my browser as the issue.

For interacts, looks like "input_grid" and "color_selector" widgets
have problems. To reproduce:

@interact
def f(a = input_grid(nrows=0, ncols=0)):
pass

(throws a syntax error about an internal file)

@interact
def f(a = color_selector()):
print a

(widget mis-renders in my browser. I took screenshots, but I don't
know where to upload the images.)

The other interact widgets I tested all work.

Note that all of the above results were correct as of last night. For
some reason, none of the interacts or plots is working for me this
morning.

Anyways, that was my attempt at hammering it. :-)

Kelvin

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

On 7/30/11 9:14 AM, Benjamin Jones wrote:
> On Fri, Jul 29, 2011 at 7:11 PM, Jason Grout
> <jason-sage@creativetrax.com> 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 in
>> any webpage. This is the start of a comprehensive Sage web service as well,
>> and lays a piece of the ground work for a much more scalable model for doing
>> computations in the normal notebook.
>>
>> It's ready to be hammered by the larger community at this point. I will be
>> mentioning this next week at Mathfest, so please try to break it :). I
>> think just about any normal Sage computation should work. Please report any
>> errors to me.
>>
>> We've also rewritten interacts, so please especially test interacts. There
>> are some exciting new features for interacts in this rewrite that I can
>> detail later. The main focus for this testing is that current existing
>> interacts should work unchanged, hopefully.
>>
>
> This is fantastic. I've been thinking about potential uses for this
> since I watched the recording of your talk about it at the recent Sage
> notebook days.
>
> One suggestion, is it possible to make the input text box resizeable
> so that the user can see more than 15 lines at a time? I didn't look
> into the docs closely so maybe this is already an option.

I experimented with having the edit box auto-grew up to about 30 lines,
but it didn't seem to be quite as nice. It's a single-line change to
the CSS to make it autogrow (with upper and lower limits).

Would you suggest making the box auto-grow? How many lines do you think
it should have at minimum or maximum?

Thanks,

Jason

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

On 7/30/11 7:57 AM, John Travis wrote:
> Awesome.
>
> A real minor problem I found was with labels in interact. No latex
> for such as
>
> def _( x0 = input_box(0,width=5,label='$x_0$'), blah


I noticed this when testing one of your interacts yesterday and created
an issue for it:
https://github.com/jasongrout/simple-python-db-compute/issues/168


>
> Also, %hide does not work but it would be nice to have the option when
> shelling out from something like WebWork. Indeed, when using
> interacts, it might be nice to be able to turn off everything else
> other than the interactive output window and an evaluate button.
> Maybe the addition of %hide command in this context would turn off the
> code box (other than some small way to get it back), "Upload files",
> and all but the latest session.


You can already include code in the html of the page, which is
automatically picked up when you create the singlecell. I haven't tried
turning off the edit box after you do that (it would be easy to use CSS
to hide the edit box and/or make it non-editable). This is definitely
in the plans to make this work nicely, though. One of the major uses
will be interacts that are seamlessly embedded in webpages (i.e., just
the controls and the output).

Thanks for your testing and suggestions!

Jason

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] public single cell server

On Fri, Jul 29, 2011 at 7:11 PM, Jason Grout
<jason-sage@creativetrax.com> 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 in
> any webpage.  This is the start of a comprehensive Sage web service as well,
> and lays a piece of the ground work for a much more scalable model for doing
> computations in the normal notebook.
>
> It's ready to be hammered by the larger community at this point.  I will be
> mentioning this next week at Mathfest, so please try to break it :).  I
> think just about any normal Sage computation should work.  Please report any
> errors to me.
>
> We've also rewritten interacts, so please especially test interacts. There
> are some exciting new features for interacts in this rewrite that I can
> detail later.  The main focus for this testing is that current existing
> interacts should work unchanged, hopefully.
>

This is fantastic. I've been thinking about potential uses for this
since I watched the recording of your talk about it at the recent Sage
notebook days.

One suggestion, is it possible to make the input text box resizeable
so that the user can see more than 15 lines at a time? I didn't look
into the docs closely so maybe this is already an option.

Thanks!

--
Benjamin Jones

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Citing used Sage components automatically

On Fri, Jul 29, 2011 at 7:50 AM, Niles <nilesj@gmail.com> wrote:
>
> Indeed, one of the things that first piqued my curiosity was the
> message when quitting a Sage session: "Exiting spawned Maxima
> process." or "Exiting spawned Gap process."  Another approach to
> raising user awareness might be to have each component of Sage
> "register" its use in a session, even if it doesn't require spawning a
> new process.  Then the list of used components could be printed when
> quitting a session.  But can this be done without adding tons of
> overhead?
>
> -Niles
>

+1

Something like "Today's Sage session brought to you by ... "

--
Benjamin Jones

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

Awesome.

A real minor problem I found was with labels in interact. No latex
for such as

def _( x0 = input_box(0,width=5,label='$x_0$'), blah

Also, %hide does not work but it would be nice to have the option when
shelling out from something like WebWork. Indeed, when using
interacts, it might be nice to be able to turn off everything else
other than the interactive output window and an evaluate button.
Maybe the addition of %hide command in this context would turn off the
code box (other than some small way to get it back), "Upload files",
and all but the latest session.

JT

On Jul 30, 5:34 am, Jason Grout <jason-s...@creativetrax.com> wrote:
> On 7/30/11 3:25 AM, leif wrote:
>
>
>
>
>
>
>
>
>
>
>
> > On 30 Jul., 10:48, Jason Grout<jason-s...@creativetrax.com>  wrote:
> >> On 7/30/11 1:35 AM, John Cremona wrote:
>
> >>> Looks nice!  Is it necessary to have the "Computation ID" block so
> >>> visible?  After a few evaluations I could no longer see the output
> >>> without scrolling down.
>
> >> No, it's not necessary; thanks for the suggestion.  In fact, when
> >> embedding in a page, you can turn on or off any of those things.  I just
> >> updated things to move that computation id below the results, though.
> >> Is that better?
>
> > Yep, to me it is.
>
> > It would also be nice to have some indicator showing whether the
> > computation is still running.
>
> This ishttps://github.com/jasongrout/simple-python-db-compute/issues/161
>
>
>
> > (Usually I would just change the "Evaluate" button, but that is
> > apparently also used to restart the current computation.)
>
> > I wonder if it would make sense to have an [optional?] scroll bar for
> > the output as well. In that case, I would even put the output box
> > *above* the input / code box (like pocket calculators, phones and IRC
> > clients have it ;-) ). But perhaps that's also customizable when
> > embedding it into a page.
>
> Yep; all of this is customizable when embedding into a page.  Just set
> the sizes, positions, and CSS however you want.
>
>
>
> > I observed that the output is interspersed with additional blank lines
> > (one or more in sequence), depending on how fast the server delivers.
>
> This is nowhttps://github.com/jasongrout/simple-python-db-compute/issues/174
>
> Thanks,
>
> Jason

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

On 7/30/11 3:25 AM, leif wrote:
>
> On 30 Jul., 10:48, Jason Grout<jason-s...@creativetrax.com> wrote:
>> On 7/30/11 1:35 AM, John Cremona wrote:
>>
>>> Looks nice! Is it necessary to have the "Computation ID" block so
>>> visible? After a few evaluations I could no longer see the output
>>> without scrolling down.
>>
>> No, it's not necessary; thanks for the suggestion. In fact, when
>> embedding in a page, you can turn on or off any of those things. I just
>> updated things to move that computation id below the results, though.
>> Is that better?
>
> Yep, to me it is.
>
> It would also be nice to have some indicator showing whether the
> computation is still running.


This is https://github.com/jasongrout/simple-python-db-compute/issues/161

>
> (Usually I would just change the "Evaluate" button, but that is
> apparently also used to restart the current computation.)
>
> I wonder if it would make sense to have an [optional?] scroll bar for
> the output as well. In that case, I would even put the output box
> *above* the input / code box (like pocket calculators, phones and IRC
> clients have it ;-) ). But perhaps that's also customizable when
> embedding it into a page.


Yep; all of this is customizable when embedding into a page. Just set
the sizes, positions, and CSS however you want.

>
>
> I observed that the output is interspersed with additional blank lines
> (one or more in sequence), depending on how fast the server delivers.
>

This is now
https://github.com/jasongrout/simple-python-db-compute/issues/174

Thanks,

Jason


--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

On 30 Jul., 10:48, Jason Grout <jason-s...@creativetrax.com> wrote:
> On 7/30/11 1:35 AM, John Cremona wrote:
>
> > Looks nice!  Is it necessary to have the "Computation ID" block so
> > visible?  After a few evaluations I could no longer see the output
> > without scrolling down.
>
> No, it's not necessary; thanks for the suggestion.  In fact, when
> embedding in a page, you can turn on or off any of those things.  I just
> updated things to move that computation id below the results, though.
> Is that better?

Yep, to me it is.

It would also be nice to have some indicator showing whether the
computation is still running.

(Usually I would just change the "Evaluate" button, but that is
apparently also used to restart the current computation.)

I wonder if it would make sense to have an [optional?] scroll bar for
the output as well. In that case, I would even put the output box
*above* the input / code box (like pocket calculators, phones and IRC
clients have it ;-) ). But perhaps that's also customizable when
embedding it into a page.


I observed that the output is interspersed with additional blank lines
(one or more in sequence), depending on how fast the server delivers.


-leif

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

I have tested multiple interacts of mine and some computations, and everything seems to work quite well except for the backslash \, which I tried to use to split lines. It gives a syntax error:

SyntaxError                               Traceback (most recent call last) SyntaxError: invalid syntax (<string>, line 57)
The line number depends on the length of the code.

Anyway, well done :)

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: 4.7.2.alpha0?

On 29 Jul., 23:37, Francois Bissey <francois.bis...@canterbury.ac.nz>
wrote:
> On Fri, 29 Jul 2011 13:44:01 kcrisman wrote:
> > So it would be helpful to have some clarification, if only to avoid
> > rebasing.
>
> What I did last time I had a problem like that was to make my ticket dependent
> of the ticket already in the unofficial release. That way there is an explicit
> dependency chain.

Of course, but not really a solution.

What happens if the patch(es) / ticket(s) you based your changes on
get unmerged again for some reason? The same as if you hadn't based
your ticket on the "candidate(s)" but these stay in.
And people wanting to try / review your ticket (patchbot included)
also need to apply the whole, perhaps "artificially grown" dependency
chain. Things get worse with spkgs that require rebuilding others or
applying some patches in addition.

There's no stays-merged probability field for the tickets on the
list... ;-)
(And trying to judge that from the "candidate" tickets is more work,
if at all possible, since further tickets you probably didn't think of
because they weren't listed might break them at any time.)


I actually ran into the situation having to rebase a patch of an
already (quite long) positively reviewed ticket on a new patch merged
into devel release N+2 (N: current official devel version).

I provided an alternate patch for that version, and in fact the ticket
I rebased the patch to still remained in version N+2 when it was
officially announced quite a while later, but my ticket now again
needs review, thereby delaying another positively reviewed one which
depends on the former. [Maybe it would have gotten re-reviewed if I
attached the rebased patch earlier, but who wants to test against an
unofficial release with in general arbitrary dependencies?]


IMHO the more or less volatile (nobody knows) unofficial releases
cause more confusion, at least if one follows Francois' suggestion and
"ignores" what the README.FIRSTs state:

"[...] There is no point in testing it. [...]"

"That being said, it can still be useful to use a non-released Sage
version for rebasing a patch, but don't complain if the version
changed and broke your patch. [...]" (The older ones didn't say that
IIRC.)

A few people will base their patches on the current devel, others on
some uncertain, sometimes frequently changing future release.

Things would be a little easier if trac supported different branches,
though it wouldn't be clear whether some dependencies are of
functional or just "syntactical" nature.


-leif

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

On 7/30/11 1:35 AM, John Cremona wrote:
> Looks nice! Is it necessary to have the "Computation ID" block so
> visible? After a few evaluations I could no longer see the output
> without scrolling down.

No, it's not necessary; thanks for the suggestion. In fact, when
embedding in a page, you can turn on or off any of those things. I just
updated things to move that computation id below the results, though.
Is that better?

Thanks,

Jason

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: public single cell server

Looks nice! Is it necessary to have the "Computation ID" block so
visible? After a few evaluations I could no longer see the output
without scrolling down.

This looks as if it could be very useful!

John

On Sat, Jul 30, 2011 at 7:05 AM, Jason Grout
<jason-sage@creativetrax.com> wrote:
> On 7/29/11 8:15 PM, P Purkayastha wrote:
>>
>> Hi,
>> Some computations ran fine. However, the code from
>> http://wiki.sagemath.org/interact/ didn't. Only the first order is
>> shown, and moving the slider provides no update.
>
>
> Thanks.  That is fixed now.
>
> Jason
>
> --
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this group, send an email to
> sage-devel+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

วันศุกร์ที่ 29 กรกฎาคม พ.ศ. 2554

[sage-devel] Re: public single cell server

On 7/29/11 8:15 PM, P Purkayastha wrote:
> Hi,
> Some computations ran fine. However, the code from
> http://wiki.sagemath.org/interact/ didn't. Only the first order is
> shown, and moving the slider provides no update.


Thanks. That is fixed now.

Jason

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: public single cell server

Hi,
 Some computations ran fine. However, the code from http://wiki.sagemath.org/interact/ didn't. Only the first order is shown, and moving the slider provides no update.
  basu.

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] public single cell server

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
in any webpage. This is the start of a comprehensive Sage web service
as well, and lays a piece of the ground work for a much more scalable
model for doing computations in the normal notebook.

It's ready to be hammered by the larger community at this point. I will
be mentioning this next week at Mathfest, so please try to break it :).
I think just about any normal Sage computation should work. Please
report any errors to me.

We've also rewritten interacts, so please especially test interacts.
There are some exciting new features for interacts in this rewrite that
I can detail later. The main focus for this testing is that current
existing interacts should work unchanged, hopefully.

Thanks especially to Ira Hanson and Alex Kramer for doing much of the
design and implementation work (funded by Drake University and the NSF),
to William for an early version, and Fernando Perez and Robert Bradshaw
for many helpful conversations. I'm sure there are people I've missed
who have contributed in some way; please let me know if I've missed someone!

The repository for the code is:
https://github.com/jasongrout/simple-python-db-compute. The
instructions are not quite up to date, but I'll be working on those soon.

Thanks,

Jason

--
Jason Grout

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: 4.7.2.alpha0?

On Fri, 29 Jul 2011 13:44:01 kcrisman wrote:
> On Jul 29, 4:20 pm, Volker Braun <vbraun.n...@gmail.com> wrote:
> > On Friday, July 29, 2011 9:16:10 PM UTC+1, kcrisman wrote:
> > > More seriously, it would be helpful to know "how official" such non-
> > > releases are.
> >
> > Not at all official.
>
> 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 thing!) they must
> have some additional status than someone else's random fork-y 4.7.2,
> right?
>
> So it would be helpful to have some clarification, if only to avoid
> rebasing.
>
What I did last time I had a problem like that was to make my ticket dependent
of the ticket already in the unofficial release. That way there is an explicit
dependency chain.

Francois

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: 4.7.2.alpha0?

On Jul 29, 4:20 pm, Volker Braun <vbraun.n...@gmail.com> wrote:
> On Friday, July 29, 2011 9:16:10 PM UTC+1, kcrisman wrote:
>
> > More seriously, it would be helpful to know "how official" such non-
> > releases are.
>
> Not at all official.

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 thing!) they must
have some additional status than someone else's random fork-y 4.7.2,
right?

So it would be helpful to have some clarification, if only to avoid
rebasing.

- kcrisman

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: problem with plot_step_function

My guess is that the problem is "floatiness", given the following
three data points.

1) sage: line([(10000000000000000, 2), (10000000000000001, 2),
(10000000000000002, 2)]) doesn't work either.

2) From line2d?? we are led to this:

Definition: sage.plot.plot.xydata_from_point_list(points)
Source:
def xydata_from_point_list(points):
r"""
Returns two lists (xdata, ydata), each coerced to a list of
floats,
which correspond to the x-coordinates and the y-coordinates of the
points.


3)

sage: float(10000000000000000)
10000000000000000.0
sage: float(10000000000000001)
10000000000000000.0


I can't think of a workaround right now, but I imagine the problem is
that all the input points (perhaps output too) are being made into one
thing or something. Jason or Robert might have better ideas.

I hope this helps in some way, sorry I don't have a better answer.

- kcrisman

On Jul 21, 1:58 pm, kstueve <kevin.stu...@gmail.com> wrote:
> When I call
>
> plot_step_function(v=[(10000000000000000, 279238341033925),
> (10000000000000001, 279238341033925), (10000000000000002,
> 279238341033925), (10000000000000003, 279238341033925),
> (10000000000000004, 279238341033925), (10000000000000005,
> 279238341033925), (10000000000000006, 279238341033925),
> (10000000000000007, 279238341033925), (10000000000000008,
> 279238341033925), (10000000000000009, 279238341033925),
> (10000000000000010, 279238341033925), (10000000000000010,
> 279238341033925)], vertical_lines=True)
>
> I get a blank graph.  Is there a workaround, or should I open a new
> trac ticket?
>
> Kevin Stueve

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: 4.7.2.alpha0?

On Friday, July 29, 2011 9:16:10 PM UTC+1, kcrisman wrote:
More seriously, it would be helpful to know "how official" such non-
releases are.

Not at all official. 

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: 4.7.2.alpha0?

Should be at http://sage.math.washington.edu/home/release/sage-4.7.2.alpha0/

In fact, Jeroen has started work on alpha1 :)

More seriously, it would be helpful to know "how official" such non-
releases are. Especially while trying to update spkgs, it seems weird
to work on 4.7.1.rcx instead of 4.7.2.alphay...

On Jul 29, 3:30 pm, John Cremona <john.crem...@gmail.com> wrote:
> Jeroen,
>
> I see that you have started merging tickets into 4.7.2.alpha0 (which
> is surely another indication that 4.7.1 will be released soon!).  As I
> am working on a file which has been affected by one such merge, can
> you remindme where I can find the not-yet-announced 4.7.2.alpha0 -- or
> should I just wait until you announce it?
>
> John

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] 4.7.2.alpha0?

On Fri, 29 Jul 2011 20:30:49 John Cremona wrote:
> Jeroen,
>
> I see that you have started merging tickets into 4.7.2.alpha0 (which
> is surely another indication that 4.7.1 will be released soon!). As I
> am working on a file which has been affected by one such merge, can
> you remindme where I can find the not-yet-announced 4.7.2.alpha0 -- or
> should I just wait until you announce it?
>
Hi John,

All that stuff released and not officially released is available at
http://sage.math.washington.edu/home/release/
You may note he has even started "composing" 4.7.2.alpha1.
Of course until it is released it is still "in motion".

Francois

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: porting sage to OS X 10.7

On Jul 28, 4:33 pm, William Stein <wst...@gmail.com> wrote:
> On Wed, Jul 27, 2011 at 10:54 AM, William Stein <wst...@gmail.com> wrote:
> > On Tue, Jul 26, 2011 at 10:06 PM, William Stein <wst...@gmail.com> wrote:
> >> Hi Sage Developers,
> >> To help with porting Sage to OS X 10.7, I bought 10.7, installed it, and
> >> setup a public-facing machine (actually, the old bsd.math.washington.edu)
> >> with OS X 10.7 and *XCode 4.1* installed on it.    If you had an account on
> >> the old bsd.math.washington.edu computer, then you automatically still have
> >> an account on this computer.   It's
> >>             sqrt5.cs.washington.edu
> >> So try to build Sage!   Report and fix issues.
>
> > Quick report -- Mike Hansen started working on this.
>
> > So far he has fixed the problems with readline and BoehmGC, and he
> > appears to have built *all* the rest of Sage on OS X 10.7 using XCode
> > 4.1, except scipy and ECL/Maxima.  And he reports "I don't think the
> > scipy one looks too hard."
>
> I think he dealth with the scipy one.    Building ECL (lisp!) is the
> current remaining blocker.
>

While Mike et al. are at it, Juanjo is in the process of getting ready
to release (yes, I know that means "not today") a different ECL that
will deal with the Cygwin issue, so you might want to see if he has a
pre-release version for this. Just throwing it out there....

- kcrisman

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] 4.7.2.alpha0?

Jeroen,

I see that you have started merging tickets into 4.7.2.alpha0 (which
is surely another indication that 4.7.1 will be released soon!). As I
am working on a file which has been affected by one such merge, can
you remindme where I can find the not-yet-announced 4.7.2.alpha0 -- or
should I just wait until you announce it?

John

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Citing used Sage components automatically

On Jul 28, 2:35 pm, Jason Grout <jason-s...@creativetrax.com> wrote:
> I find the two responses here very interesting.  From Niles and John's
> responses, it sounds like this feature could help users turn into
> developers as their curiosity about the algorithms gets the better of
> them and they started poking around in the internals of Sage.

Indeed, one of the things that first piqued my curiosity was the
message when quitting a Sage session: "Exiting spawned Maxima
process." or "Exiting spawned Gap process." Another approach to
raising user awareness might be to have each component of Sage
"register" its use in a session, even if it doesn't require spawning a
new process. Then the list of used components could be printed when
quitting a session. But can this be done without adding tons of
overhead?

-Niles

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Sage/Singular days - Kaiserslautern - Sept 26-30

Hi,

there will be a Sage/Singular workshop in Kaiserslautern, Germany on
September 26-30, 2011.

http://wiki.sagemath.org/days34

The main focus of the meeting will be to improve libSingular and the
Sage - Singular interface.

We anticipate a coding oriented event with few talks. Newcomers,
especially those interested in C-level usage of Singular or writing
Sage interfaces are welcome. So far we did not plan any tutorial
sessions, but some veterans will be present to answer questions.

We have limited funding to support travel and accommodation costs.
Please write to the organizers if you need financial support.


There is no registration fee or a formal application procedure. If you
plan to participate, please add your name to the list on the wiki page

http://wiki.sagemath.org/days34

or contact the organizers. This will help us with the local
arrangements.


Looking forward to seeing you there.

Cheers,
Burcin

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Graph Theory Quick Reference

Yeahhhhhhhh !! Great stuff :-)

Small things you could like to add, depending on the use you intended for your pdf :

Construction of graph through addition*multiplication :

G = 2*g + 3*h (where g and h are graphs)

or one of the most frequent loops in graph algorithms :

iterating over vertices :
for v in g:

iterating over edges :

for u,v in g.edges(labels = False):
for u,v,l in g.labels():

If it were just me I would have put a "NP-Hard problems" section, but I know that's not really relevant in a quickref guide :-D

otherwise :

add_edges appears twice
I spotted a "Cpython"

The commands (edge/vertex)_disjoint_paths, (edge/vertex)_connectivity and flow would perfectly fit in the connectivity section. And the "matching" method we have in Sage is much worthier of being on your quickref than TSP/Steiner/... of the NP-Hard section I mentionnd previously  :-)

Well, even if you do not like *any* of those suggestions, thank you again for this file ! ;-)

Nathann

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

วันพฤหัสบดีที่ 28 กรกฎาคม พ.ศ. 2554

[sage-devel] Re: Graph Theory Quick Reference

Very nice! Several suggestions - that are just that, suggestions.

I'd move "matrices" to be right next to "linear algebra." Maybe
include .characteristic_polynomial() in the linear algebra section.

I don't see ".diameter()" anywhere.

A section on "constructions"? You have "products", but there are
other ways to make new graphs, such as the line graph.

You could do a "properties"
section. .is_forest(), .is_interval(), .is_regular(), some selection
of the most important of the ".is_" methods you do not have already in
other places.

As Minh said, a handful of pre-built graphs, either useful infinite
families, or one-off classic examples, would be a good addition.

A couple of graphics would make it more visually appealing. Maybe
some information on plotting (which is sometimes confusing). You
could give an example plot command, and include the resulting output/
graphic (hopefully without cut-off vertices).

Where you have "graph." repeatedly, you could probably use "G." and
save yourself a bit of room on each line. And I'd think something
like G.is_isomorphic(H) would be apparent to most readers,
especially when the roles of G and H are interchangeable.

When I did one of these for linear algebra, I did not try to be too
precise about all of the data types and options, unless it was a
frequent "gotcha" or a key feature. I had just a small section on
"help", things like tab-completion, which you could recycle in this if
you wished.

Rob

--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org