g1 = DiGraph({1:[2]})
print type(g1.vertices()[0])
g2 = DiGraph({3:[4]})
print type(g2.vertices()[0])
g3 = DiGraph({13:[14]})
print type(g3.vertices()[0])
outputs
Is this a bug? If not, what is the rationale behind this?
--
Jori Mäntysalo
On Wed, 5 Aug 2015, William Stein wrote:
There's a (depressing) discussion about this problem here:
http://stackoverflow.com/questions/27214065/how-to-docstring-in-python-for-multiple-languages
Assuming we would have all the needed software, how would we use them?
Let's assume that foo(x) is
I particularly like the menu on the left hand side (more than the amount
that I particularly like the website).
That's not to say I disagree with Dima. The menu could slide in and out on
mouseover.
One general comment I have about the site is that on first impression it
looks slightly square a
At http://trac.sagemath.org/ticket/17164 it seems that Sage 6.8 has not
support for vulnerable SSLv3 anymore. But it still seems to have - at
least on SageNB.
Can someone clarify this? I have and old installation that I have upgraded
version-by-version for years. Is this bug only for those? Or
In order to streamline updating third-party tarballs I've written a small
web app where you can directly upload them. That way you don't need to host
files yourself. Plus, the files can be retrieved by sha1 so with a little
bit more scripting I won't always forget to manually copy them to the
m
Thanks for all the discussion and hints about working with the left
sidebar. I like Dima's suggestion of a 2-up mode.
You'll notice we did not center the fixed-width text in the browser
window. We are reserving the real-estate on the right for some generally
useful purpose, though we have not
>
>
> Looks like everything is linked correctly. The following suggests that there
> is a bug in DYLD_LIBRARY_PATH handling in the OSX 10.11 betas:
>
> https://forums.developer.apple.com/message/31148
>
> Possibly thats an intentional change of the spec to fix the (still unpatched
> on all re
I just updated the tarballs to fix an issue noted with the MSVC build.
Note, this only affects Windows when building with MSVC, hence I didn't
push the patch number.
Bill.
On 7 August 2015 at 23:33, Bill Hart wrote:
> Hi all,
>
> We are very pleased to present Flint version 2.5.0. It can be dow
Looks like everything is linked correctly. The following suggests that
there is a bug in DYLD_LIBRARY_PATH handling in the OSX 10.11 betas:
https://forums.developer.apple.com/message/31148
Possibly thats an intentional change of the spec to fix the (still
unpatched on all released OSX versions)