Talk:Heronian triangles: Difference between revisions

Content added Content deleted

Inline

Revision as of 07:00, 25 October 2015

The Python part is badly formatted and does not show up in the index, someone who knows wiki-formatting should fix it --Zorro1024 (talk) 14:21, 22 March 2015 (UTC)

Fixed. The problem was Smoe's R entry which was not terminated properly (and which should have gone after the python entry rather than before it). --Rdm (talk) 16:27, 22 March 2015 (UTC)

I wonder if a spark of static or noise entered the Python version at some point in its editing history ? On my system the current draft overgenerates triangles, giving a different output from that shown. (It seems to find 1383 rather than 517 triangles). If not an editing glitch then possibly an artefact of changing Python versions ? I am running Python 2.7.10 on OS X 10.11. Hout (talk) 00:12, 25 October 2015 (UTC)

The solution originally just worked for Python 3. I've added the necessary __future__ import. --Andreas Perstinger (talk) 07:00, 25 October 2015 (UTC)

Revision as of 00:12, 25 October 2015 (view source) Hout (talk \| contribs) (Python draft corrupted ? or Python version issue ? Appears to be overgenerating) ← Older edit		Revision as of 07:00, 25 October 2015 (view source) rosettacode>AndiPersti (Python should work now for version 2 too) Newer edit →
Line 3:		Line 3:

	::I wonder if a spark of static or noise entered the Python version at some point in its editing history ? On my system the current draft overgenerates triangles, giving a different output from that shown. (It seems to find 1383 rather than 517 triangles). If not an editing glitch then possibly an artefact of changing Python versions ? I am running Python 2.7.10 on OS X 10.11. [[User:Hout\|Hout]] ([[User talk:Hout\|talk]]) 00:12, 25 October 2015 (UTC)		::I wonder if a spark of static or noise entered the Python version at some point in its editing history ? On my system the current draft overgenerates triangles, giving a different output from that shown. (It seems to find 1383 rather than 517 triangles). If not an editing glitch then possibly an artefact of changing Python versions ? I am running Python 2.7.10 on OS X 10.11. [[User:Hout\|Hout]] ([[User talk:Hout\|talk]]) 00:12, 25 October 2015 (UTC)

			:::The solution originally just worked for Python 3. I've added the necessary <code>__future__</code> import. --[[User:AndiPersti\|Andreas Perstinger]] ([[User talk:AndiPersti\|talk]]) 07:00, 25 October 2015 (UTC)