Am 2014-11-15 um 19:29 schrieb Volker Braun:
> Works for me, possibly because I have a newer git.
$ git --version
git version 2.1.3
Can it be that it works for you because the commit
ec0aae9358f5204a3db6406b2c2f2818a78f5892 (this is the actual commit of #16747)
is contained in your local reposito
Hello !
> Here are some links to discussions that look to me have gone astray.
Also, as you might notice
> that some of the participants in these discussions have since ceased to
post on the public
> mailing lists, even though they were active contributors/developers
before:
Ahahaha. Such a long
Hello everybody !
On 16 November 2014 01:48, john_perry_usm wrote:
>
> (1) When switching development to Git, it became harder for the less
> talented to contribute. I'm not the only one who encountered a complete
> recompilation of Sage when reviewing a new ticket -- even one that didn't
> touch
Hello,
We currently have two much implementation of 2x2 matrices. I found at
least three that leads to distinct element classes
sage: M1 = SL2Z
sage: M2 = MatrixSpace(ZZ,2)
sage: from sage.matrix.matrix_integer_2x2 import MatrixSpace_ZZ_2x2
sage: M3 = MatrixSpace_ZZ_2x2()
sage: m1 = M1([2,1,1,1]
On 11/15/14 11:47 AM, mmarco wrote:
> I am afraid i would need more information to make a decission about this. I
> wasn't aware of the existence of the problems you mention. Without knowing
> what happened in those cases, i cannot say if the
> proposed code of conduct would have been a good idea
On Sun Nov 16 2014 at 12:44:39 AM Anne Schilling
wrote:
> On 11/15/14 7:32 AM, P Purkayastha wrote:
> >
> >
> > On Friday, November 14, 2014 8:50:14 PM UTC+8, Dr. David Kirkby (Kirkby
> Microwave Ltd) wrote:
> >
> > On 13 November 2014 18:48, Volker Braun > wrote:
> > > and welcome every
> +1 This is a HUGE problem and you're definitely not the first to complain
> to me about it.
Sorry, I'm not trying to complain about it, and I've read the motivation
for the change, and I understand it. I wouldn't want the people who
advocated it to infer some of us are ungrateful; this i
On Sat, Nov 15, 2014 at 12:18 PM, john_perry_usm wrote:
> William
>
>> Understand, there are also consequences to not having some sort of
>> successful code of conduct. These include:
>>
>>1. Continuing to lose talented Sage developers specifically because
>> they do not feel comfortable wit
William
Understand, there are also consequences to not having some sort of
> successful code of conduct. These include:
>
>1. Continuing to lose talented Sage developers specifically because
> they do not feel comfortable with the tone of the lists, and
>
Can you give an example of this
On Sat, Nov 15, 2014 at 11:16 AM, Nathann Cohen wrote:
> Yo !
>
>> Understand, there are also consequences to not having some sort of
>> successful code of conduct. These include:
>
> Hmmm It is a bit incorrect to pretend that none of it would ever happen
> if we had a code of conduct. A cod
I am afraid i would need more information to make a decission about this. I
wasn't aware of the existence of the problems you mention. Without knowing
what happened in those cases, i cannot say if the proposed code of conduct
would have been a good idea to prevent them or not.
--
You received
Yo !
> Understand, there are also consequences to not having some sort of
> successful code of conduct. These include:
Hmmm It is a bit incorrect to pretend that none of it would ever happen
if we had a code of conduct. A code is just a tool to say that those who
wrote the code are a priori
On 15 November 2014 19:08, John Cremona wrote:
> On 15 November 2014 18:57, William Stein wrote:
>> I installed the huge stein-watkins-ecdb optional spkg,
>>
>> sage -i stein-watkins-ecdb
>>
>> but it is also broken when used:
>>
>> sage: p = SteinWatkinsPrimeData(10)
>> sage: p.next()
>>
On 15 November 2014 18:57, William Stein wrote:
> I installed the huge stein-watkins-ecdb optional spkg,
>
> sage -i stein-watkins-ecdb
>
> but it is also broken when used:
>
> sage: p = SteinWatkinsPrimeData(10)
> sage: p.next()
> ...
> IOError: The Stein-Watkins data file
> /usr/local/
I installed the huge stein-watkins-ecdb optional spkg,
sage -i stein-watkins-ecdb
but it is also broken when used:
sage: p = SteinWatkinsPrimeData(10)
sage: p.next()
...
IOError: The Stein-Watkins data file
/usr/local/sage/sage-6.4/local/share/stein_watkins/p.10.bz2 must be
installed.
Yo !
> Aaah you would have been a perfect German had you been born on the other
> side of the border ;-)
>
> Where is the threat of punishment in Kant's categorical imperative?
Ahahahah. I had never heard of that thing ! And love this way of
looking at things.
+1 to making Kant's categorical imp
On Sat, Nov 15, 2014 at 9:37 AM, Nathann Cohen wrote:
> -1 to a code of conduct, and +1 to considering that sage-devel is just yet
> another human community with no specfic rules needed.
>
> I was reading a law book on contracts recently, and it just feels wrong to
> have yet another example of a
Probably works:
git remote update trac && git trac checkout 16747
The issue is that git does not let you checkout individual sha1's, they
might have been part of a branch that has been removed intentionally (e.g.
somebody accidentally checked in their password etc).
On Saturday, November 15, 2
Hi,
I guess the upgrade to patch broke more optional packages:
sage -i normaliz
...
gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
patching file source/Makefile.configuration
(Stripping trailing CRs from patch; use --binary to disable.)
patching f
On Sat, Nov 15, 2014 at 10:02 AM, Im, Mee Seong wrote:
> Hi,
>
> I'm trying to use Ore_algebra* in
> http://www.risc.jku.at/research/combinat/software/ore_algebra/ via sagemath.
>
> Can you tell me how I can implement this package to cloud.sagemath.com?
It is already pre-installed for all project
On Saturday, November 15, 2014 5:37:16 PM UTC, Nathann Cohen wrote:
>
> Plus it feels weird to have another "rule" without a clearly defined
> sanction.
>
Aaah you would have been a perfect German had you been born on the other
side of the border ;-)
Where is the threat of punishment in Kant's
Hi,
i just had the same problem with #15316 (and had to use a similar
workaround):
$ git trac checkout 15316
Loading ticket #15316...
Checking out Trac #15316 remote branch
969de52313ee407d874e9f7b318111c144de534e -> local branch
t/15316/969de52313ee407d874e9f7b318111c144de534e...
Traceback (mos
The reason for the failure is that we updated patch and it is now less
lenient with malformed patches.
On Saturday, November 15, 2014 5:49:50 PM UTC, William wrote:
>
> Installing the brian optional package via "sage -i brian" seems broken
> in Sage-6.4:
>
> sage: !sage -i brian
> Found packa
On Sat, Nov 15, 2014 at 9:49 AM, William Stein wrote:
> Installing the brian optional package via "sage -i brian" seems broken
> in Sage-6.4:
I think the solution should be to remove brian as a Sage optional
package, since one can just as well do
sage: !pip install brian
and that seems to actua
The release manager recently closed ticket #16747, but it is not yet in develop.
In that time window, git trac checkout (or the equivalent git fetch trac
commit_id) fails.
$ git trac checkout 16747
Checking out Trac #16747 remote branch ec0aae9358f5204a3db6406b2c2f2818a78f5892
-> local branch t/16
Installing the brian optional package via "sage -i brian" seems broken
in Sage-6.4:
sage: !sage -i brian
Found package brian in /usr/local/sage/sage-6.4/upstream/brian-1.4.1.p0.spkg
brian-1.4.1.p0
Extracting package /usr/local/sage/sage-6.4/upst
On 15 November 2014 16:44, Anne Schilling wrote:
>> > Code of Conduct
>
> Thanks for the links to the guidelines. It is interesting to see how other
> communities handle this.
> Dave's question was how situations will be handled when a violation occurs or
> that are reported.
> Does your com
-1 to a code of conduct, and +1 to considering that sage-devel is just yet
another human community with no specfic rules needed.
I was reading a law book on contracts recently, and it just feels wrong to
have yet another example of a contract which is *not* designed with all
sides equal. If you
On 11/15/14 7:32 AM, P Purkayastha wrote:
>
>
> On Friday, November 14, 2014 8:50:14 PM UTC+8, Dr. David Kirkby (Kirkby
> Microwave Ltd) wrote:
>
> On 13 November 2014 18:48, Volker Braun > wrote:
> > and welcome everyone to
> > vote on it.
> >
> >
> > Code of Conduct
>
Hi!
On 2014-11-15, P Purkayastha wrote:
> You can just follow some guidelines. I am a member of the Gentoo Linux
> forums and they have very clear statements saying what is considered
> inappropriate in the forums. In gist,
>
> 1. No personal attacks,
> 2. No offensive language
That's where we
On 14 November 2014 14:29, Ondřej Čertík wrote:
>
> On Nov 14, 2014 11:30 AM, "Bill Page" wrote:
>>
>> What do you mean by "the real derivative"?
>
> The absolute value doesn't have a complex derivative, but it has a real
> derivative, over the real axis.
>
It seems to me that the concept of "re
On Friday, November 14, 2014 8:50:14 PM UTC+8, Dr. David Kirkby (Kirkby
Microwave Ltd) wrote:
>
> On 13 November 2014 18:48, Volker Braun >
> wrote:
> > and welcome everyone to
> > vote on it.
> >
> >
> > Code of Conduct
> > ---
>
> > If you believe someone is violating the c
On Friday, November 14, 2014 7:06:56 AM UTC-8, kcrisman wrote:
>
>
>> If person A verbally attacks person B, I still think it does not help to
>> show a *disapproving* reaction towards person A, because then A may feel
>> attacked, which may make his/her behaviour even worse, and which
>> woul
My main dev machine is inaccessible so I will have to postpone this.
François
> On 12/11/2014, at 10:22, François Bissey
> wrote:
>
> On Tue, 11 Nov 2014 13:18:20 Jean-Pierre Flori wrote:
>> On Tuesday, November 11, 2014 10:12:33 PM UTC+1, François wrote:
>>> I guess the compiler requirement wi
IMHO the most convenient place is to look in the git history, this also
works if you don't currently have internet access for starters. The
git-trac script implements this:
$ git trac find 4f8b380
Commit has been merged in 6.4.rc1.
commit 24c666295fcc1c157503fc212057c27253825099
Merge: 28c5157 b
It had never occurred to me that such a thing would ever be necessary.
Any exclusions should be collective decisions not by some oligarchy,
and should allow for reinstatement if the perpetrators are contrite.
John
On 15 November 2014 08:49, Andrew wrote:
> In an ideal world I think that a code o
In an ideal world I think that a code of conduct would not be necessary.
Sadly, the world is not ideal.
I think that SImon's example of what happened with the German translation
project is a great example of why it would be good to have a code of
conduct: some one's comments turned him off work
Am 2014-11-13 um 17:46 schrieb kcrisman:
> Unfortunately, we no longer use the "Merged in" part of Trac, which was a VERY
> efficient way to find this out. Searching through git history and then trying
> to forward to the next release is something for git wizards, no doubt some
> command using tag
38 matches
Mail list logo
