Am 25.05.2012 11:31, schrieb Aaron Meurer:
You shouldn't have to worry about it, though, because if you run
./bin/use2to3 that uses Python 3, thanks to the shebang line.
Ah, that's good to know.
I'll consider that when doing the writeup for the testing environment.
My current plan is to do a writeup of "how to run the test suite", and add a
section to the workflow document. (Which has become far too long and is
serving different purposes, so I'm also thinking about splitting it up.)
That would be fine. Also, figuring out how to make section links
(i.e., the table of contents) work correctly in GitHub's wiki would
help a lot.
I'll see what I can do.
Yes, the Apple ecosystem has a bad policy on security upgrades, too.
That's because you have to balance security upgrades with
compatibility.
Well... there isn't much of a trade-off if you find your hand forced by
malware authors. You'll have to get your security act together or watch
your reputation crumble.
Apple seems to be hellbent on learning that the hard way.
(Apple users seem to accept and support that stance. Well, whatever -
time will tell.)
By the way, their policy isn't so bad. They dropped Python 2.5
support in Mac OS X 10.7 (the most recent version). I couldn't find
at what point Python 2.5 stopped being supported, but I imagine it was
at some point between the two Mac OS X releases, if not later.
Heh. Better late than never.
Apple still registers as "unusually late". Which is going to hurt them a
lot once the botnet herders really start targetting Apple. Windows is
getting harder and harder to break, so Apple would be the logical next
choice on the list.
We'll see :-)
Running system scripts with an interpreter that has known unfixed bugs is
just inviting a privilege escalation, so if Apple ever gets their act
together, Python will be among the first things in the upgrade pipeline (and
possible one of those that take longer, so I'm still not holding my breath).
This talk of security is pointless.
On whether to keep or drop 2.5 support: Agreed.
On whether we should add proper warning: Strongly disagreed.
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sympy?hl=en.
