3 ms·
Just wanted to add that 1) this is freaking awesome, and 2) some of the formatting gets messed up and makes the answer difficult to read. For instance... well,
by d23 14y ago
Just wanted to add that 1) this is freaking awesome, and 2) some of the formatting gets messed up and makes the answer difficult to read. For instance... well, actually I don't know how to link directly to one of the answers. Scroll down to "Difference between __str__ and __repr__ in Python" on this page[1]. I was having difficulty understanding the sentences, then I realized they were actually bullet points put together.
[1] http://www.stack-ed.com/#tag/python/user/14343/Ned http://www.stack-ed.com/#tag/python/user/14343/Ned Batchelder
- gknoy 14y ago> http://www.stack-ed.com/#tag/python/user/14343/Ned http://www.stack-ed.com/#tag/python/user/14343/Ned Batchelder Also, URLs with spaces in them appear to be harder to share, in that they are not always automatically hyperlinked correctly. Would you consider using dashes (or underscores) in place of the dash in the stack-ed URLs?
- nirvanatikku 14y agoFair point. That portion of the URL is simply used for display purposes, so I can pretty much do anything; dashes, underscores, or encode it as a URI component. Seems that dashes/underscores are preferred?
- LukeShu 14y agoURLs can't contain spaces; the space needs to be "URL-encoded" ("%20"). Many browsers these days render URL-encoded characters in the URL bar. Firefox (actually Iceweasel) 18 handles this by displaying a space in the URL bar, but "%20" when I copy/paste it. Without doing any extra work, just copy pasting that URL after visiting it: http://www.stack-ed.com/#tag/python/user/14343/Ned%20Batchelder http://www.stack-ed.com/#tag/python/user/14343/Ned%20Batchel... Having URL-encoded values certainly is a usability problem, however, I do think that this should be registered as a bug with whatever browser you are using.