NOTE: Check https://github.com/nineteendo/for-any-each for the latest version. The problem Recently, #118946 was merged, replacing any() with a for loop: -return any(key in m for m in self.maps) +for mapping in self.maps: + if key in mapping: + return True +return False Why? Because any…

I replaced “every” with “each” as that’s 1 character shorter and still grammatically correct.

Please re-read this post from 2 days ago. You’re still throwing out half-baked ideas and it’s becoming quite annoying. [image] Alternative call syntax Ideas That’s not entirely true. Yes, library changes will get pushback of the form “why can’t this be on PyPI”, but that …

[image] Alternative call syntax All you are doing, as has already been mentioned, is using up people’s patience with you to the point where you’re going to start getting ignored and your ideas dismissed. Sorry, it feels like I already used up your patience with me in my previous posts. So, you…

[image] Nice Zombies: [image] barneygale: You’re still throwing out half-baked ideas and it’s becoming quite annoying. Do you think that because I replaced “every” with “each”, indicating that the details might not be finalised yet? Or because I don’t have an implementation for this idea? …

[image] Cornelius Krupp: Modifying the comprehension syntax is fundamentally the wrong idea. You want to add a new syntax that looks like Comprehensions. Do you have a better idea? Implementing this without using any new keywords is hard. I’m happy to drop this in case we can do this without…

[image] Nice Zombies: Do you have a better idea? Implementing this without using any new keywords is hard. I’m happy to drop this in case we can do this without using the comprehension syntax though. That’s not my point. I do somewhat like the syntax, although I don’t think it’s all that cle…

[image] Cornelius Krupp: Surely quantified_comprehensions can only ever result in one value? Otherwise you need to describe the semantics better, since I don’t know how you expected that to potentially result in multiple values. Yes, that’s why they need to be split up from unquantified_compr…

I got similar timing benchmarks from 1000 items. There’s absolutely no need for new syntax, but perhaps it’s food for thought about the implementation of any and all. But if 1000 iterations in 90 microseconds isn’t fast enough for some application, perhaps Python is not the best tool for it in the…

[image] James Parrott: perhaps it’s food for thought about the implementation of any and all That’s sadly not possible, they are regular builtin functions (no keyword), all they see is a generator. [image] James Parrott: if 1000 iterations in 90 microseconds isn’t fast enough for some a…

[image] Nice Zombies: Sorry, it feels like I already used up your patience with me in my previous posts. You have used up a LOT of people’s patience. Probably more people than you realise - you won’t know how many people just see your name and move on. Or maybe have even blocked you, so they …

For any & every

Python Help

barneygale (Barney Gale) May 14, 2024, 3:19pm 3

Please re-read this post from 2 days ago. You’re still throwing out half-baked ideas and it’s becoming quite annoying.