Re: backslash in triple quoted string
Left Right writes: > Then it just means that the grammar lies. The two claims are mutually > exclusive, so either one is a lie or the other or both. [...] A couple of points. First, the convention in this and most other Usenet newsgroups is to write new text *below* any quoted text. This is known as "bottom-posting". The alternative, "top-posting" is common in email in some environments, but tends to cause confusion on Usenet. It's also a good idea to trim any quoted text that's not relevant to your followup. See most of the other followups in this newsgroup, including this one, for examples. Even if you happen to prefer top-posting, I suggest trying to follow the existing conventions observed by the vast majority of participants here. Second, the word "lie" is far more harsh than what I presume you meant to say. For me, and I think for most people, the word "lie" implies a deliberate intent to deceive. I don't think you actually believe that the authors of the documentation you're complaining about deliberately inserted false information with the goal of deceiving readers. If you want to say that the grammar is incorrect, or contains an error, that's something that can be discussed reasonably. If you say that it "lies", you're making a claim of malice and making assumptions about someone else's state of mind with no real basis. Perhaps that's not what the word "lie" means to you, but I suggest that it explains the harsh reaction to your initial statement. -- Keith Thompson (The_Other_Keith) [email protected] void Void(void) { Void(); } /* The recursive call of the void */ -- https://mail.python.org/mailman/listinfo/python-list
Re: backslash in triple quoted string
> But the message doesn't say it's an error. It uses the word "warning", > not "error". You're tilting at a straw horse here. Read the associate release note. -- https://mail.python.org/mailman/listinfo/python-list
Re: backslash in triple quoted string
> Second, the word "lie" is far more harsh than what I presume > you meant to say. For me, and I think for most people, the word > "lie" implies a deliberate intent to deceive. No, it doesn't. Consider Joseph Conrand's Heart of Darkness, the final episode where Marlow comes to Kurtz' widow and tells her about how her husband died. He lies to her, but his intent is not to deceive her, instead, he intends to make sure that her delusion of her late husband is unharmed and that she continues to live that delusion because he judges she will be better off for it. In fact, you yourself used the word deceit, which is to lie with intention to benefit from a lie. But people tell lies for all sorts of reasons. People can lie by omission, through embellishment, by choosing to focus on less relevant aspects of the event. All of these are lies. When a painter mixes white paint into the form shadow of a plaster ball, she lies. When Google Maps puts the destination marker of the restaurant you have a reservation in in the middle of a sea, it lies. English literature lessons aside, even if you believe what you believe about the meaning of the word, you could at least try to find the irony, that was the larger goal, than to immediately presume you are being attacked, and start retaliating instead of looking into the problem. -- https://mail.python.org/mailman/listinfo/python-list
PyCon
Anyone going to PyCon? I'll be there, getting in Tuesday night. -- https://mail.python.org/mailman/listinfo/python-list
Re: backslash in triple quoted string
Left Right writes: >> Second, the word "lie" is far more harsh than what I presume >> you meant to say. For me, and I think for most people, the word >> "lie" implies a deliberate intent to deceive. > > No, it doesn't. Consider Joseph Conrand's Heart of Darkness, No, thank you. I am trying to help you to understand how people are reacting to your posts. I suggested that saying that the grammar is incorrect or contains an error would have expressed exactly what you intended without triggering hostile reactions, which I'm assuming you don't want. [...] > English literature lessons aside, even if you believe what you believe > about the meaning of the word, you could at least try to find the > irony, that was the larger goal, than to immediately presume you are > being attacked, and start retaliating instead of looking into the > problem. I'm not aware that I have been attacked or that I have retaliated. (No need to explain why you might think I have.) One more thing: your Usenet or email client probably adds an attribution line above any quoted text. I urge you to leave it in place. It makes the discussion easier to follow, especially for those of us who read the comp.lang.python Usenet newsgroup rather than the mailing list. I do not intend to reply further. -- Keith Thompson (The_Other_Keith) [email protected] void Void(void) { Void(); } /* The recursive call of the void */ -- https://mail.python.org/mailman/listinfo/python-list
Re: backslash in triple quoted string
On 13/05/25 6:28 am, Left Right wrote: Read the associate release note. I take it you're referring to this: In a future Python version, SyntaxError will eventually be raised, instead of SyntaxWarning. (Contributed by Victor Stinner in gh-98401.) That doesn't contradict what I said. Currently it's a warning. If and when it becomes an error, presumably the grammar documentation will be updated to reflect that. If it isn't, you'll have cause to complain, but not before. -- Greg -- https://mail.python.org/mailman/listinfo/python-list
Re: backslash in triple quoted string
Chris and Oleg (sp?), please control your tempers; your latter posts added nothing useful to the conversation. (Apologies for the late reply, I was out of town.) -- ~Ethan~ Moderator -- https://mail.python.org/mailman/listinfo/python-list
