Hi,
Le jeudi 30 janvier 2020 04:06:02 UTC+1, Vipul Gupta a écrit :
>
>
> Yeah Sage works fine after that. But I wanted to contribute to sage and
> therefore config my git trac account as mentioned in the this link
> https://doc.sagemath.org/html/en/developer/git_trac.html
>
>
Welcome to Sage de
Hi Eric,
On 2020-01-30, Eric Gourgoulhon wrote:
> I would even vote for removing the git-trac section from the developer
> manual.
-1
I do use "git trac".
Best regards,
Simon
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe fr
On Thu, Jan 30, 2020 at 7:35 AM Simon King wrote:
> Hi Eric,
>
> On 2020-01-30, Eric Gourgoulhon wrote:
> > I would even vote for removing the git-trac section from the developer
> > manual.
>
> -1
>
> I do use "git trac".
>
Agreed. I would absolutely not advocate removing git-trac from the
ma
I think git-trac should not be mentioned in the manual as the preferred way
to use git.
Imho the majority of devs here use plain git...
On Thu, 30 Jan 2020, 14:07 David Roe, wrote:
>
>
> On Thu, Jan 30, 2020 at 7:35 AM Simon King wrote:
>
>> Hi Eric,
>>
>> On 2020-01-30, Eric Gourgoulhon wrot
Can someone help me with guidelines to make contribution using only git?
Regards
Vipul Gupta
On Thu, 30 Jan, 2020, 7:45 pm Dima Pasechnik, wrote:
> I think git-trac should not be mentioned in the manual as the preferred
> way to use git.
>
> Imho the majority of devs here use plain git...
>
> On
Are you familiar with using github server and CLI to checkout specific
branches and pushing into a github repo?
(there are excellent tutorials on this).
In fact, you can create your own fork of sagemath on github and practice
there.
Our workflow is similar, except that it has a much cruder web in
Hi Dima,
On 2020-01-30, Dima Pasechnik wrote:
> I think git-trac should not be mentioned in the manual as the preferred way
> to use git.
OK. Stating that "being able to use plain git is a useful skill" is
fine, and of course elaborating how to use plain git to work with trac
is fine, too. But p
Yeah I am familiar with github and its features. But I am not sure how to
incorporate ticket features of sage issues and contribute to them?
Briefly, I want to ask how to work with tickets using git only. There are
no clear manuals for this also.
Regards
Vipul Gupta
On Thu, 30 Jan, 2020, 9:01 pm D
On Thu, 30 Jan 2020, 15:37 Vipul Gupta, wrote:
> Yeah I am familiar with github and its features. But I am not sure how to
> incorporate ticket features of sage issues and contribute to them?
> Briefly, I want to ask how to work with tickets using git only. There are
> no clear manuals for this a
There's a probem with multiple substitutions in Sage 9.0.
sage: var('x,y')
(x, y)
sage: (*1*/x)(x=*1*/y, y =*42*)
42
Sage 8.1 gives the following, which is the correct behavior
sage: var('x,y')
(x, y)
sage: (*1*/x)(x=*1*/y, y =*42*)
y
--
You received this message because you are
On Thursday, January 30, 2020 at 8:54:56 AM UTC-8, Ties Laarakker wrote:
>
> There's a probem with multiple substitutions in Sage 9.0.
>
>
>
> sage: var('x,y')
>
> (x, y)
>
> sage: (*1*/x)(x=*1*/y, y =*42*)
>
> 42
>
>
> That is indeed very strange an worrisome. For further diagnostics: this
also h
On Wednesday, January 29, 2020 at 3:04:12 PM UTC-8, Vipul Gupta wrote:
>
> Hello,
> I am using Ubuntu 18.04.3 LTS with sage version 9.1 beta 2
> After using below command
> git clone git://github.com/sagemath/sage.git
> cd sage
> git checkout develop
> make
>
Okay up to here. Before doing the n
On the stackexchange site there is now an initial attempt to fix this,
which is unfortunately not working on my computers. However, maybe others
are luckier
Martin
Am Sonntag, 26. Januar 2020 09:07:10 UTC+1 schrieb Martin R:
>
> I asked the same question at
> https://emacs.stackexchange.com/q
Am Dienstag, 28. Januar 2020 00:41:55 UTC+1 schrieb Michael Orlitzky:
>
> The insertion order is part of the language as of python-3.7, and can't
> be changed:
>
> * https://mail.python.org/pipermail/python-dev/2017-December/151283.html
> * https://docs.python.org/3.7/tutorial/datastructures.htm
On Thursday, January 30, 2020 at 12:52:06 PM UTC-8, Markus Wageringel wrote:
>
> From the different options mentioned here, my preferred choices are
>
> 2c) `pretty_print(D, sort=True)` for clarity, or
>
> 2d) `dict(sorted(D.items()))` for simplicity, as this makes use of
> well-known functions an
On Thursday, January 30, 2020 at 1:17:14 PM UTC-8, Nils Bruin wrote:
>
> prints as 'The Sage display manager using the IPython command line
> backend' and 'The Sage display manager using the IPython notebook backend'
> respectively, so they're already distinguishable. Setting different
> default
On 1/30/20 3:52 PM, Markus Wageringel wrote:
>
> While the order of dictionaries is insertion order now, functions in
> Sage or in libraries that return dictionaries usually do not make any
> promise about the order in which elements are inserted into the
> dictionary. Thus, when doctesting such a
Rather than distinguishing the different backends, I was more worried about how
to keep what related doctests currently give us. For example, in
src/doc/fr/tutorial/latex.rst, pretty_print is advertised as a way to obtain
nicely formatted MathJax output:
sage: pretty_print(x^12)
\newcom
> Am 30.01.2020 um 23:10 schrieb Michael Orlitzky :
>
> This is a good point, but it's a problem we already have. We don't make
> any promises about the precise message contained in e.g. a ValueError,
> but we still frequently test the contents. You just update it when you
> change the message.
Hello,
I'm trying to build Sage 9.0 from source on CentOS 7.5.1804 and it fails
with:
"Error installing package sqlite-329"
Here is the ".../sage-9.0/logs/pkgs/sqlite-329.log" log file that the
error message says to include:
https://pastebin.com/SCy98UXK
The two main messages that jump
> " WARNING: 'aclocal-1.15' is missing on your system." Which seems
unimportant since it's followed with the text "You only need it if..." with
reasons that don't pertain to me.
One possible reason is that somehow the timestamps for the files got messed
up. Easiest solution would be to install aut
21 matches
Mail list logo
