Python script isn't producing text in data file
Steven D'Aprano
steve at pearwood.info
Wed Dec 10 21:41:55 EST 2014
On Thu, 11 Dec 2014 12:44:51 +1100, Chris Angelico wrote:
> Agreed. There are ways around some of those problems (eg using wget to
> fetch something, and then looking at it in a text editor - it's hard to
> get pwned through a text editor... though I won't say impossible), but
> there are other issues too, and all in all, it's just best to include
> the text in-line.
I believe that there was a recently discovered exploit on Linux where
viewing a file with "less" could run arbitrary code.
But really, if the program is short enough, you should include the code
in the body of your post, or at least as an attachment. And if it is not
short enough, you should *make it shorter*.
http://sscce.org/
There are many reasons why people might not click through links to
download your code:
- they may be reading your post somewhere where they have access
to email, but not web (e.g. behind a corporate firewall)
- they may not appreciate the security risks
- they might just be lazy, and firing up a web browser too much
a distraction
- they might already have 200+ tabs open in their browser, and
adding one more may be just enough to shift them from "yes,
I'd love to help" to "fuck 'em, they can solve their own
problems".
--
Steven
More information about the Python-list
mailing list