On Tuesday, July 5, 2016 at 9:31:04 AM UTC+2, Dima Pasechnik wrote:
>
> Yes that tarball has the goods. I’ll wait for a new 1.2.2-xx tarball
>> though. No self respecting
>> packager wants to deal with an upstream tarball which changes all the
>> times.
>
>
> We had this argument already. If
I notice anaconda ship its own openssl, on OS X at least.
Are they purposefully avoid GPL in all their packages?
François
> On 2/12/2016, at 11:47, Volker Braun wrote:
>
> On OSX, you can do either
>
> a) nothing => no https support,
>
> a) supply the (missing) openssl headers for the system
On Linux, you can build Sage with and without openssl. If you ever hit the
network you really should build with openssl(-devel) available, it will be
picked up automatically. But its not a requirement. Though we should
probably strongly recommend it in the installation instructions.
GnuTLS and
Dear Thierry,
Thank you for this answer : you have done a large work that I planned for
my next opportunity. Comments below :
Le jeudi 1 décembre 2016 22:56:15 UTC+1, Thierry (sage-googlesucks@xxx) a
écrit :
>
> Hi,
>
> On Sun, Nov 27, 2016 at 03:52:59AM -0800, Emmanuel Charpentier wrote:
> >
Hi,
On Sun, Nov 27, 2016 at 03:52:59AM -0800, Emmanuel Charpentier wrote:
> OK. Let's try again :
> I have two questions :
>
>1. What are the parts (standard, optional or experimental, except, of
>course, the openssl package itself) of Sage that need (directly or
>indirectly) a secu
Hi Travis,
Thanks, I did not know that...
On Thursday, 1 December 2016 16:35:55 UTC+2, Travis Scrimshaw wrote:
>
> Hey Peleg,
>You should also only define the reference (i.e., the .. [XYZ] part) in
> the master references file in doc/en/reference/references/index.rst.
>
> Best,
> Travis
>
>
Hey Peleg,
You should also only define the reference (i.e., the .. [XYZ] part) in
the master references file in doc/en/reference/references/index.rst.
Best,
Travis
On Thursday, December 1, 2016 at 7:58:00 AM UTC-6, Sébastien Labbé wrote:
>
> $ cat file.rst
>
> Cite many times the same item
$ cat file.rst
Cite many times the same item [ABCDEF]_ [ABCDEF]_ is okay.
.. [ABCDEF] bibliography
Many times the same item [XYZ]_ in bibliography in the same file is not
okay.
.. [XYZ] bibliography1
.. [XYZ] bibliography2
labbe@priminfo tmp $ rst2html file.rst file.html
file.rst:9: (WARNING
But perhaps I have to be more precise.
In the docstring I also have a link to the reference, something of the form
[ABC123]_. I've read something about "anonymous links", but I am not sure I
understood the difference. I keep searching.
On Thursday, 1 December 2016 15:23:56 UTC+2, Peleg Michaeli
Yes.
On Thursday, 1 December 2016 14:47:28 UTC+2, Dima Pasechnik wrote:
>
> did you try "make doc-clean" and then rebuilding the docs?
>
> On Thursday, December 1, 2016 at 11:58:12 AM UTC, Peleg Michaeli wrote:
>>
>> I have a method, and in the docsrting of this method I have references. I
>> the
did you try "make doc-clean" and then rebuilding the docs?
On Thursday, December 1, 2016 at 11:58:12 AM UTC, Peleg Michaeli wrote:
>
> I have a method, and in the docsrting of this method I have references. I
> then want to alias the method. Something like this:
>
> class Class(object):
>
I have a method, and in the docsrting of this method I have references. I
then want to alias the method. Something like this:
class Class(object):
def method(self):
r"""
REFERENCES::
.. [ABC123] A, B and C in 123, 123.
"""
alia
12 matches
Mail list logo
