On Sunday, April 6, 2014 11:17:12 PM UTC+2, Volker Braun wrote:
>
> Git cheat sheet:
> http://boxen.math.washington.edu/home/vbraun/doc/git-cheat-sheet.pdf
>
$ git trac checkout 13853
Loading ticket #13853...
Checking out Trac #13853 remote branch public/13853 -> local branch
t/13853/public/138
On Sunday, 6 April 2014 15:00:13 UTC-6, Jesus Escribano wrote:
>
> Hello
> i'm trying a new installation, and I got exactly the same error.
> Any idea?
>
> Jesús
>
>
I had to do
./sage -sh -c "easy_install backports.ssl-match-hostname"
before installing the package - this way this thing is down
On Sun, Apr 6, 2014 at 2:17 PM, Volker Braun wrote:
> I'm changing the developer guide to push people towards git + my "git trac"
> subcommand instead of the "sage -dev" scripts. Nothing actually changes as
> far as functionality goes, you can still use the dev scripts or just 100%
> plain git.
A
or without the -c, don't remember.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sa
On Sunday, April 6, 2014 11:34:45 PM UTC+2, Evan Oman wrote:
>
> Alright so total noob question here but how do I make these changes to the
> rpy2 files?
>
> I tried unpacking the tarball in the upstream folder(??), made the
> appropriate changes, and then repackaged it but now I get a checksum
Alright so total noob question here but how do I make these changes to the
rpy2 files?
I tried unpacking the tarball in the upstream folder(??), made the
appropriate changes, and then repackaged it but now I get a checksum error.
Is there some sort of touch or other command I need to use to upd
I'm changing the developer guide to push people towards git + my "git trac"
subcommand instead of the "sage -dev" scripts. Nothing actually changes as
far as functionality goes, you can still use the dev scripts or just 100%
plain git.
As Karl-Dieter pointed out, the updated developer guide no
Yo !
> It's not "self" that matters, it's the result returned by the cached method
> that shouldn't contain any UniqueRepresentation object that was constructed
> using self. That's expensive to check.
Oh. I see :-/
Nathann
--
You received this message because you are subscribed to the
On Sunday, April 6, 2014 1:35:17 PM UTC-7, Nathann Cohen wrote:
>
> No, I meant... Can't we add some parameter to cached_method, so that
> it could not be applied to an object which inherits from
> UniqueRepresentation (if this is the problem) ?
>
> something like
>
> def cached_method(self, fu
Hello
i'm trying a new installation, and I got exactly the same error.
Any idea?
Jesús
El lunes, 3 de marzo de 2014 22:21:04 UTC+1, Andrey Novoseltsev escribió:
>
> On Saturday, 1 March 2014 19:39:13 UTC-7, jason wrote:
>>
>> I just updated the sagecell spkg:
>>
>> http://boxen.math.washington
Helloo !!!
> If you mean by "automatic": write a script to create a lot of them and throw
> them away and see if it leaks then, yes. Otherwise: this really is a
> non-local program logic problem, so detecting it is hard.
No, I meant... Can't we add some parameter to cached_method, so that
it
On Sunday, April 6, 2014 12:23:56 PM UTC-7, Nathann Cohen wrote:
>
> > As you can see for n=6, all the 318
> sage.graphs.linearextensions.LinearExtensions instances are still in
> memory. I suspect it's something like this:
> > - The "linear_extension" method is cached. This means that the pose
> As you can see for n=6, all the 318
sage.graphs.linearextensions.LinearExtensions instances are still in
memory. I suspect it's something like this:
> - The "linear_extension" method is cached. This means that the poset
will keep the linear_extension alive
> - The unique_parent of linear_exten
On Sunday, April 6, 2014 4:40:35 PM UTC+2, Sebastien Gouezel wrote:
>
> Le 06/04/2014 13:45, Sebastien Gouezel a écrit :
> > I am also trying to compile sage (6.2 beta 4) under Cygwin. I got a
> > working copy of sage, but the doc does not build (so, I can not try
> > "make test"). Here is the
We are now up to alpha4. New changes should only affect Mac. Thanks Leif!
http://mpir.org/mpir-2.7.0-alpha4.tar.bz2
http://mpir.org/mpir-2.7.0-alpha4.tar.lz
http://mpir.org/mpir-2.7.0-alpha4.zip
Bill.
On 6 April 2014 18:53, leif wrote:
> Bill Hart wrote:
>
>> Can you tell me what the changes
The following paradigm happens for
"sage.combinat.posets.posets.FinitePoset" and their "linear_extensions",
but it's such an easy mistake to make that I'd almost consider it a flaw in
our design:
class A(Parent,UniqueRepresentation):
@cached_method
def BfromA(self):
ret
Bill Hart wrote:
Can you tell me what the changes are so I can merge them?
diff -Naur mpir-2.7.0-alpha3/configure mpir-2.7.0-alpha3-patched/configure
--- mpir-2.7.0-alpha3/configure
+++ mpir-2.7.0-alpha3-patched/configure
@@ -25408,7 +25408,7 @@
# Defined in mpn/x86_64/x86_64-de
On Saturday, April 5, 2014 7:41:47 PM UTC-7, Andrew Juell wrote:
>
> Running sage locally under Ubuntu to avoid any esoteric problems in the
> cloud, I discovered another issue...while I could iterate over Posets(7)
> and (8) and count their linear extensions with little trouble, attempting
> to
Can you tell me what the changes are so I can merge them?
Bill.
On 6 April 2014 18:03, leif wrote:
> leif wrote:
>
>> Ok, here's minimalist's quick'n'dirty temporary solution;
>> minimally-invasive in that it touches only one file and affects only
>> Darwin x86_64 :-) :
>>
>> --- mpir-2.7.0-al
leif wrote:
Ok, here's minimalist's quick'n'dirty temporary solution;
minimally-invasive in that it touches only one file and affects only
Darwin x86_64 :-) :
--- mpir-2.7.0-alpha2/configure.ac
+++ mpir-2.7.0-alpha2/configure.ac
@@ -2843,15 +2843,18 @@
;;
64)
+ GM
Le 06/04/2014 13:45, Sebastien Gouezel a écrit :
I am also trying to compile sage (6.2 beta 4) under Cygwin. I got a
working copy of sage, but the doc does not build (so, I can not try
"make test"). Here is the beginning of the log:
Building reference manual, first pass.
[combinat ] Configurati
On 6 April 2014 15:44, Денис Крыськов wrote:
>
>
> On Sunday, April 6, 2014 3:18:20 PM UTC+4, Bill Hart wrote:
>>
>> OK, according to this page:
>>
>> http://en.wikipedia.org/wiki/List_of_Intel_Core_i5_microprocessors
>>
>> your processor has an Intel Sandy Bridge core, with avx support.
>>
>> ..
v=9
f = open('posetstats', 'w')
P=Posets(v)
Bean=0
for p in P:
Bean+=1
if Bean%1000==0: print Bean
f.write(str(Bean)+ " "+ str(len(p.cover_relations()))+"
"+str(p.linear_extensions().cardinality())+"\n")
print "done"
f.close()
--
You received this message because you are subscr
I am also trying to compile sage (6.2 beta 4) under Cygwin. I got a
working copy of sage, but the doc does not build (so, I can not try
"make test"). Here is the beginning of the log:
Building reference manual, first pass.
[combinat ] Configuration error:
[combinat ] There is a syntax error in
OK, according to this page:
http://en.wikipedia.org/wiki/List_of_Intel_Core_i5_microprocessors
your processor has an Intel Sandy Bridge core, with avx support.
According to this page:
http://gcc.gnu.org/onlinedocs/gcc-4.8.1/gcc/i386-and-x86_002d64-Options.html
this is the right option (ok, it
On 6 April 2014 09:53, Денис Крыськов wrote:
>
>
> On Sunday, April 6, 2014 10:12:36 AM UTC+4, 袁轶君 wrote:
>>
>> Well, I solved my problem. MPIR can only be built in a pure ASCII
>> path...No UNICODE characters is allowed. Besides that ,I have a question.
>> What's the difference between lib_mpir_
Running sage locally under Ubuntu to avoid any esoteric problems in the cloud,
I discovered another issue...while I could iterate over Posets(7) and (8) and
count their linear extensions with little trouble, attempting to do so with the
9-element posets overnight resulted in python eating up 4+G
27 matches
Mail list logo
