725 karma · joined January 12, 2012
So if Canada tries to make friends with anyone other than the US, it's a hostile act?
Makes it all the more obvious that USA is Canada's abusive partner, that they should have broken up with a long time ago.
Other than the current tariff narrative, it's fairly standard CIA play when we look at what they did to Latin America already.
Is that not one of Intel's trademarks from the past 20 years?
There is justification for it for sure (see https://github.com/osmandapp/OsmAnd/issues?q=is%3Aissue+slow... for a few), and I love OSM out of principle, but as a product, it will remain my last resort until the user experience is tolerable.
1. There is no citation on the sentence, "Recent evidence has found that no level of alcohol consumption is safe for health." This is really the only line we are interested in.
2. There is no comparison on the effects of alcohol on the body by dosage (and frequency), which is, again, what is required from the brief to make that claim.
Again, while I don't necessarily disagree with what's in the report, and that it is already established that drinking too much is not good for the heart, considering many otherwise toxic substances have a hormetic zone, it is critical that a study like this rules out the its existence for ethanol.
I use "Find Usages" on foo to see where it is used. Once you see where it is used, you know what the types can be. It's not great, but it's also something that can be progressively remedied.
In the event that the function is not as trivial as your example suggests, the author should have written a docstring to help you understand what it is trying to do, in addition to type annotations that will make it more readable.
In this example, bar can either be a function, a class, or any object with __call__(), so the type information is less important in this case, than actual docstrings that express intent.
There should be one-- and preferably only one --obvious way to do it.
the author used two different ways of hyphenating (three, if you count the whole PEP 20). PEP 20 is clearly not meant to be taken as law. Nor PEP 8. Nor PEP 257.People frequently mistake "one obvious way" with "one way". There are lots of ways to iterate through something, for example, but there is really one obvious way. And the philosophy here still applies: when you read anyone else's python code, the obvious way is probably doing the obvious thing. I think that is the more appropriate takeaway from PEP 20.
The stimulating nature of extremism makes it really hard for a new platform to be pro-"sensible free speech".
- Standing applies pressure on the same points on the feet. Walking shifts pressure from place to place.
- "Moving in general is good for health" (with the implication that sitting and standing still are not moving)
This "low profile blue switch" uses a click bar, so the click you hear does not correspond to the actuation point exactly---which I am a bit bummed about---but I hear the majority of low profile clicky switches currently have the same implementation/issue.
* The error code C2006 assumes there is a clear divide between "smaller" and "larger" strings. What is smaller, and what is larger? Is 1000 large? Is 5000 large? Is 1000000 large? If I want my comment to be capped at 5000 characters to encourage healthy discussions but prevent spamming, is it large?
* If a field has no "known format" and that's where it draws the line between CharField and TextField, then why is the error C2006 still raised when TextField(max_length=5000) is used? Why does the validator recommend allowing anyone to insert entries of unlimited size?
If I'm on postgres and actually want my comments to have a max length of 5000, is it suggesting that using CharField(max_length=5000) is a problem with my design? Using CharField / VARCHAR vs TextFIeld / TEXT should not have a performance difference in postgresql.
I forgot what made github.com switch to github.io. Something similar but totally separate.
It's an Easter egg.