Hello folks,
this is 3.0.2.rc0, the likely final release of the 3.0.2 series
and hopefully next to identical to the final 3.0.2. What is new?
* Franco Saliola and Peter Jipsen's posets and semi-lattive
patch
* Robert Miller's self-orthogonal binary codes
* Bjarke Hammersholt Roune's Frobby
Is there any reason why John Boyer's planarity code isn't an spkg?
- Robert
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group a
I vote for Proposal B.
John
On May 21, 10:02 pm, Nick Alexander <[EMAIL PROTECTED]> wrote:
> > Wow! In that case I revise my viewpoint on this matter. That's
> > really interesting. It is amazing how many things in Sage were
> > written to make Sage easier for "random undergrads", but turn
>
mabshoff wrote:
> Out of curiosity: Did you take today's CVS since the anon ecl CVS
> trees were corrupted until about two, three hours ago?
I am working with ECL built from anonymous CVS from around May 14.
I haven't been able to update from CVS since then; apparently the
anonymous CVS server w
I attach some Pari code which computes various things, including
Nagell's algorithm, including forward and reverse transforms.
Accompanying it is some test code which attempts to verify that the
inverse transform does what it is supposed to, i.e. it composes with
the forward transform to give the
On May 23, 10:42 am, mabshoff <[EMAIL PROTECTED]> wrote:
> Hello folks,
>
> this is 3.0.2.rc0, the likely final release of the 3.0.2 series
> and hopefully next to identical to the final 3.0.2. What is new?
>
> * Franco Saliola and Peter Jipsen's posets and semi-lattive
> patch
> * Robert M
On May 23, 12:55 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
Hi Robert,
> Is there any reason why John Boyer's planarity code isn't an spkg?
It was submitted as a patch and included in the library tree. Is there
any specific reason it should be in its own spkg? One reason I could
imagine is
+1. Planarity is a mess of non Cython files that are included in the
main tree and should probably be compiled as a library.
On Fri, May 23, 2008 at 9:05 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> On May 23, 12:55 pm, Robert Bradshaw <[EMAIL PROTECTED]>
> wrote:
>
> Hi Robert,
>
>> Is there any
Michael,
I just built rc0 and will test it -- but where should I be when I type
"hg update -C" ?
John
2008/5/23 mabshoff <[EMAIL PROTECTED]>:
>
>
>
> On May 23, 10:42 am, mabshoff <[EMAIL PROTECTED]> wrote:
>> Hello folks,
>>
>> this is 3.0.2.rc0, the likely final release of the 3.0.2 serie
On May 23, 5:28 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Michael,
>
> I just built rc0 and will test it -- but where should I be when I type
> "hg update -C" ?
>
> John
Hi John,
that is in $SAGE_ROOT/local/bin after sourcing local/bin/sage_env from
$SAGE_ROOT. Before runnign "hg updat
Thanks, that worked as advertised. I'm doing --testall on rc0 anyway now.
John
2008/5/23 mabshoff <[EMAIL PROTECTED]>:
>
>
>
> On May 23, 5:28 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
>> Michael,
>>
>> I just built rc0 and will test it -- but where should I be when I type
>> "hg update -C
Builds fine on an amd phenom machine running hardy heron but sage -testall
freezes at
sage -t devel/sage/sage/dsage/__init__.py (skipping) -- nodoctest.py
file in directory
sage -t devel/sage/sage/dsage/tests/testdoc.py
+
On Fri, May 23, 2008 at 4:4
On May 23, 6:09 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> Builds fine on an amd phenom machine running hardy heron but sage -testall
> freezes at
>
> sage -t devel/sage/sage/dsage/__init__.py (skipping) -- nodoctest.py
> file in directory
> sage -t devel/sage/sage/dsage/tests/testdoc.py
For what it's worth, I prefer B.
Michel
On May 23, 3:17 pm, John Cremona <[EMAIL PROTECTED]> wrote:
> I vote for Proposal B.
>
> John
>
> On May 21, 10:02 pm, Nick Alexander <[EMAIL PROTECTED]> wrote:
>
> > > Wow! In that case I revise my viewpoint on this matter. That's
> > > really interest
Jason Grout wrote:
> In the recent discussion "Change the default base_ring for matrices from
> ZZ to QQ", there were lots of opinions shared, and William summarized
> some feelings from the group, but it wasn't a solid conclusion (at
> least, based on an IRC conversation, William is rethinking
All tests passed! with rc0 + the dsage fix manually applied.
John
2008/5/23 mabshoff <[EMAIL PROTECTED]>:
>
>
>
> On May 23, 6:09 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
>> Builds fine on an amd phenom machine running hardy heron but sage -testall
>> freezes at
>>
>> sage -t devel/sage/s
Hello,
During the last bug day, I found several tickets related to
inconsistencies in abelian groups. I think I've fixed the circular
logic, etc. causing the problems in the patch included in #1284.
However, there is a difference of opinion on notation that I need to
ask about here.
Q: Should th
> Q: Should the output of
> sage: G <= H
> for G and H abelian groups be whether G is a subgroup of H?
I say yes, this is a useful notation.
> If you have a list of
> abelian groups L = [G1,...,Gn], and you want to quickly sort it
What is a "sorted list of groups"? Sorted by what? If the use
We should maintain consistency with other algebraic structures. If
G<=H means "G is a subgroup of H" when G and H are groups, then I
would similarly expect <= to mean "is a subspace of" for vector
spaces, etc. Some of these cases might be hard (number fields?); so
if the functionality is not (ye
I agree with Nick and John.
On Fri, May 23, 2008 at 12:45 PM, Robert Miller <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> During the last bug day, I found several tickets related to
> inconsistencies in abelian groups. I think I've fixed the circular
> logic, etc. causing the problems in the patch in
On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> All tests passed! with rc0 + the dsage fix manually applied.
>
> John
Cool, I have released
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc2.tar
which fixes three issues:
#3279: Michael Abshoff:
With the symbolics rewrite moving quickly, I'd like to request that if
possible people try to avoid adding more "Maxima-isms" to
sage.calculus. Specifically, if functionality is being added, please
try to keep it "general" in that the design of the functionality is
not dictated by what Maxima doe
On Fri, May 23, 2008 at 9:40 AM, Jason Grout
<[EMAIL PROTECTED]> wrote:
>
> Jason Grout wrote:
>> In the recent discussion "Change the default base_ring for matrices from
>> ZZ to QQ", there were lots of opinions shared, and William summarized
>> some feelings from the group, but it wasn't a solid
Following on from Nick's point, I cannot imagine that users will want
or expect to sort a list of groups except possibly by some criterion
provided by the user (e.g. size of the group, or something). But
apart from that we need to be able to have a default sorting or more
or less anything in Sage
What I'm doing is very simple. I've written a wrapper for the gd library,
which allows me direct and
*unsafe* access to the image data. All I have right now is functions to fetch
a matrix from the red,
green, and blue channels to a matrix, and dump data from matrices into said
channels. Ev
I expect <= to be a total order, so I prefer is_subgroup.
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.goog
I agree, which is why I supported making some sort of
canonical_comparison method for output, and then using <= for
subgroup.
On Fri, May 23, 2008 at 11:36 AM, John Cremona <[EMAIL PROTECTED]> wrote:
>
> Following on from Nick's point, I cannot imagine that users will want
> or expect to sort a l
Everything builds and tests ok out of the box for me with rc2:
All tests passed!
Total time for all tests: 2622.9 seconds
Please see /home/jec/sage-3.0.2.rc2/tmp/test.log for the complete log
from this test.
John
2008/5/23 mabshoff <[EMAIL PROTECTED]>:
>
>
>
> On May 23, 6:44 pm, "John Cremona"
mabshoff wrote:
>
>
> On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
>> All tests passed! with rc0 + the dsage fix manually applied.
>>
>> John
>
> Cool, I have released
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc2.tar
>
> which fixes th
Jaap Spies wrote:
> mabshoff wrote:
>>
>> On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
>>> All tests passed! with rc0 + the dsage fix manually applied.
>>>
>>> John
>> Cool, I have released
>>
>> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc2.tar
Jaap Spies wrote:
> mabshoff wrote:
>>
>> On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
>>> All tests passed! with rc0 + the dsage fix manually applied.
>>>
>>> John
>> Cool, I have released
>>
>> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc2.tar
> While we are at it: Somebody please change the license notes in the
> code from Apache to GPL since the code was relicensed, but that is not
> reflected in the actual source code.
>
Actually, it is not released under GPL. It's currently licensed under
Apache 2.0, which is GPL compatible. It
> Actually, it is not released under GPL. It's currently licensed under
> Apache 2.0, which is GPL compatible. It had previously been under
> Boyer's personal license.
The Apache 2.0 license is not compatible with GPLv2. I believe during
Sage Days 7, he released it (at least to Sage) under the
On Fri, May 23, 2008 at 1:16 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
>> All tests passed! with rc0 + the dsage fix manually applied.
>>
>> John
>
> Cool, I have released
>
> http://sage.math.washington.edu/home/mabshoff/release-
On Fri, May 23, 2008 at 4:02 PM, Mike Hansen <[EMAIL PROTECTED]> wrote:
>
>> Actually, it is not released under GPL. It's currently licensed under
>> Apache 2.0, which is GPL compatible. It had previously been under
>> Boyer's personal license.
>
> The Apache 2.0 license is not compatible with G
On Fri, May 23, 2008 at 4:43 PM, William Stein <[EMAIL PROTECTED]> wrote:
> On Fri, May 23, 2008 at 4:02 PM, Mike Hansen <[EMAIL PROTECTED]> wrote:
>>
>>> Actually, it is not released under GPL. It's currently licensed under
>>> Apache 2.0, which is GPL compatible. It had previously been under
>
#3291 fixes this issue and will be merged in RC3/Release in case
anyone else is having this iissue
On Fri, May 23, 2008 at 3:56 PM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> Jaap Spies wrote:
>> mabshoff wrote:
>>>
>>> On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
All tests p
Hello folks,
here we go with 3.0.2.rc3. It is basically a bunch of bug fixes
for rlm's codes code that had a couple small issues left ;)
In addition there is one pbuild issue fix that Jaap encountered
and that in the past was also hit by David Joyner. Sources are
at
http://sage.math.washington.e
Does anyone else find the printing of 0 below inconsistent?
sage: CC(0)
0
sage: RR(0)
0.000
sage: CC
Complex Field with 53 bits of precision
sage: RR
Real Field with 53 bits of precision
It doesn't always happen:
sage: RR(2)
2.00
sage: CC(2)
2.00
sage: versio
On Fri, May 23, 2008 at 10:18 PM, Nick Alexander <[EMAIL PROTECTED]> wrote:
>
> Does anyone else find the printing of 0 below inconsistent?
>
> sage: CC(0)
> 0
> sage: RR(0)
> 0.000
Yes, I agree that this is inconsistent and should be changed.
Probably the right change would be:
sage
40 matches
Mail list logo
