It's going to be a bit of a chicken and egg problem, core Python will need to prove it's worthwhile for extension devs to implement, core Python will struggle without support from extension devs. We shall see.
337 karma · joined November 9, 2020
It's going to be a bit of a chicken and egg problem, core Python will need to prove it's worthwhile for extension devs to implement, core Python will struggle without support from extension devs. We shall see.
> 99% of the users do not know what is actually trusted or not.
Before it was only 0.01% of users know what they're doing and now it's 99% of the users do not know if it's actually trusted or not, that's a 100x difference, I don't suppose you have a source on any of these numbers?
Your arguments are all hypothetical, yet we don't have to be as people literally download much of their software on PCs today outside of the Microsoft store and most users manage fine. Other mechanisms have been put in place at multiple levels (the search engine, the browser, and the OS) to make it safer for users, and the majority of those users don't get confused about trusted sources.
What do you mean by "safely" here? What is unsafe about going to a trusted APK source and downloading it and running it?
EPIC literally offers fortnite this way and users seem to manage fine: https://www.epicgames.com/fortnite/en-US/mobile/android/new-...
Before the walled gardens of the Mobile app stores it wasn't only 0.01% of users able to install software on their computers without screwing it up.
Although often confused, fairly enough as they were introduced in the same PEP, an annotation is a part of the Python syntax and type hints are a specific set of notations and ways you can use those notations inside an annotation to be used by a type hinter (yes those notations are evaluated to objects at Python runtime but the type hinter never has to be aware of that or even ever use a Python runtime).
The paper is talking about those notations inside a type hinter, not annotation objects inside a Python runtime. e.g. you can get mypy to run a turing complete program using only the notations defined in PEP 484.
But yes, if the proof is only missing easy plug-able gaps then likely a mathematician would reach out to the author so they could co-author the paper. Anything else would be rude.
I was more meaning in the case where the proof has some insight but not apply it in a way that actually disproves the Riemann Hypothesis.
Being such a short paper if people in this field thought it was close to actually disproving the Riemann Hypothesis likely another mathematician could takes the proofs concept, fix it, publish it, and have it peer reviewed to snipe the claim of disproving the Riemann Hypothesis.
Each module should use `logger = logging.getLogger(__name__)` and the logger config can set in one place, conventionally in the `__main__` script.
https://docs.python.org/3/howto/logging.html#advanced-loggin...
If a user is wanting to get or manipulate debugging information then the old frame struct will be generated when this is called.
In many countries carriers did offer unlimited sms plans, but they would cost a significant amount more over base plans which would say include 100 free texts a month. Also until EU regulations hit if you had any family or friends in other countries or ever went on holiday the cost of SMS was astronomical.
It took many carriers awhile to realize that "free" messaging apps were a significant threat, I assume because they were also charging heavily for data and just assumed because these used data they would make just as much money. Ignoring things like WiFi and how in the long run these apps would use such a small % of the data a user demanded they would be effectively free.
FYI "Google Fi" has never allowed more than 6 months abroad and it's never been a selling point for being outside the US for that length of time.
I don't think "Project Fi" was ever clear on what the maximum limit would be until at some point before 2019 (can't find when specifically) they started strictly enforcing a 6 month limit, you can find many Reddit posts at the time of people running in to this issue: https://www.reddit.com/r/ProjectFi/comments/89w4vp/extended_...
I also think there should be exceptions extenuating circumstance but even if there are significant legal barriers to provide that I think the failure here, as is often the failure with Google Fi, is the lack of communication.
Google Fi has your phone number and they have an app installed on your phone, they have multiple ways they could give you a heads up that your about to hit your abroad limit. Google Fi offers you the ability to pause your service, it would be easy enough to notify you 2 months, 1 month, 2 weeks, 1 week, and then daily that you are about to hit that termination date unless you pause your plan or return to the US. Then you could get a local sim and pause the Google Fi service with ample warning.
Yes I am quite sure for any specific niche there is a language that is better suited than Python (though I would argue with a lot of your choices there). But let's say I want a readable language that is good at data science, web backend, and provides a system glue. Python handles that much better than all the others you mentioned.
Also the one choice I am going to explicitly call out is Rust as a good systems glue language. In fact a very common practise I see now is all the good Rust libraries are getting Python bindings and made available on PyPI so all that power of Rust for systems programming can be used in Python as the glue language.
From what I remember: Insurance is one reason, Hospitals not engaging in collective bargaining (e.g. vs. NHS in England which makes decisions about what to spend money on and makes companies bid on contracts for the whole country), wasteful premium care that adds little to patient outcomes (e.g. vs Singapore which has a privatised tiered healthcare system but heavily regulates healthcare so this doesn't happen), and simply paying Doctors far more money.
The SC have also said this is a one time event and they won't accept a similar PEP in the future, modules in the future most be handled on a case by case basis and the preferred outcome will not be to remove them.
This code is all open source, literally anyone could step up and do it themselves if they had the motivation.
For reference here is the first discussions: https://discuss.python.org/t/pep-594-removing-dead-batteries... and https://mail.python.org/archives/list/python-dev@python.org/...
And nearly 3 years later here is the second discussion: https://discuss.python.org/t/pep-594-take-2-removing-dead-ba...
I thought that feedback from the first discussion was carefully considered and I'm pretty happy with take 2. I have used the some of the modules being removed but largely agree now they are either legacy or there are significantly better third party options.
In fact I would be surprised if it did get accepted as many members of the Core Dev / Steering Council have similar reservations about extending Python's Syntax as others have expressed in comments here. As demonstrated by their recent rejection of PEP 677 (Callable Type Syntax).
It's nice the broader Python community generally agrees with PEP 8 but it's always a little weird to see it referenced as an authority on styling user code when it is not it's intention and does not claim to be.
Also since Python 2.7 was made EoL there have been 2 major releases: 3.9 and 3.10.
It's interesting MacOS will be the only desktop OS used by a significant number of people to type "python" in to the command line after a fresh install and get back an unknown command error.
It's pretty clear that there were a lot of mistakes in the Python 2 to 3 transition, I'm certainly not trying to defend every choices of the developers.
I think we've seen recent languages that Strings are basically one of the hardest things to "get right". Just look at Swift and Rusts multiple attempts to implement strings even though the authors all had many years of experience of working with string implementations in other mature languages.
Python doesn't have the luxury of messing up strings, it was the number 1 reason that migrating from Python 2 to 3 took a decade. Unlike lower level compiled languages it can't stick in multiple string attempts and tell the users to pick one. So Core Devs are on the hook for maintaining any implementation for the life time of Python.
But maybe this example really was a concerted effort by someone willing to maintain Python strings for as long as needed.
Is that true?
The talk you link was about a very secretive fork of Python that Instagram was very adamant about not open sourcing until very recently (in fact it's not clear that what's open sourced is their full project).
Other than that until recently all I've ever seen is either breaking the C-API or no clear commitment from the maintainers that this was a sustained effort to support and not just a drive-by complicated patch.
In more recent times we have cinder, pyjion, pyston, and others. And CPython Devs are up-streaming either their work or their general approach.
"from __future__" is meant to only ever be used temporarily with a specific Python version slated for it becoming the default behavior.
This discussion about flags has come up recently as part of the debate of accepting PEP 649 or PEP 563 or something else continues. If the Steering Council does not accept PEP 563 it will need to be figured out how to deprecate "from __future__ import annotations" without making it the default and how to implement it's replacement.
Also in terms of mistakes codereviewdoctor twice linked to the same issue in their blog https://github.com/tensorflow/tensorflow/issues/53636 and raised the PR to the wrong project https://github.com/tensorflow/tensorflow/pull/53637 (I guess Tensorflow vendors Keras, easy mistake)
In Derek's example the switch and the bulb are 1 meter away from each other and therefore the time is 1/c seconds, i.e the time light takes to travel 1 meter.
The topic is definitely a little confusion, but there are no GR violations.
* Username and Password fields must not autocomplete * Username and Password fields must not allow text to be pasted in to the field * Password must be at least 8 characters with lower case, upper case, numbers, and special characters (they didn't care it had a maximum length of 8 characters)
I straight up told our project management it was actively hurting our security, and was told the the point here was to fulfill a regulatory requirement to complete and resolve all issues from a independent "pentest" not to improve security.