EuroPython 2020: Our Keynotes
We’re happy to announce our keynote lineup for EuroPython 2020. * EuroPython 2020 Keynotes * https://ep2020.europython.eu/events/keynotes/ Guido van Rossum - Q&A -- In this session, you’ll get a chance to get your questions answered by Guido van Rossum, our retired BDFL. In order to submit a question, please use the following Google form: Guido van Rossum Q&A: Question Submission: https://forms.gle/cAaBgUeVEBgjaDrH7 Siddha Ganju - 30 Golden Rules of Deep Learning Performance --- “Watching paint dry is faster than training my deep learning model.” “If only I had ten more GPUs, I could train my model in time.” “I want to run my model on a cheap smartphone, but it’s probably too heavy and slow.” If this sounds like you, then you might like this talk. Exploring the landscape of training and inference, we cover a myriad of tricks that step-by-step improve the efficiency of most deep learning pipelines, reduce wasted hardware cycles, and make them cost-effective. We identify and fix inefficiencies across different parts of the pipeline, including data preparation, reading and augmentation, training, and inference. With a data-driven approach and easy-to-replicate TensorFlow examples, finely tune the knobs of your deep learning pipeline to get the best out of your hardware. And with the money you save, demand a raise! Naomi Ceder - Staying for the Community: Building Community in the face of Covid-19 -- Python communities around the world, large and small are facing loss - from the loss of in person meetups and conferences to the loss of employment and even the potential loss of health and life. As communities we are all confronting uncertainty and unanswered questions. In this talk I would like to reflect on some of those questions. What are communities doing now to preserve a sense of community in the face of this crisis? What might we do and what options will we have for coming events? How can we build and foster community and still keep everyone safe? What challenges might we all face in the future? What sources of support can we find? What are our sources of optimism and hope? Alejandro Saucedo - Meditations on First Deployment: A Practical Guide to Responsible Development As the impact of software increasingly reaches farther and wider, our professional responsibility as developers becomes more critical to society. The production systems we design, build and maintain often bring inherent adversities with complex technical, societal and even ethical challenges. The skillsets required to tackle these challenges require us to go beyond the algorithms, and require cross-functional collaboration that often goes beyond a single developer. In this talk we introduce intuitive and practical insights from a few of the core ethics themes in software including Privacy, Equity, Trust and Transparency. We cover their importance, the growing societal challenges, and how organisations such as The Institute for Ethical AI, The Linux Foundation, the Association for Computer Machinery, NumFocus, the IEEE and the Python Software Foundation are contributing to these critical themes through standards, policy advise and open source software initiatives. We finally will wrap up the talk with practical steps that any individual can take to get involved and contribute to some of these great open initiatives, and contribute to these critical ongoing discussions. EuroPython 2020 is waiting for you -- We’ve compiled a full program for the event: - more than 120 sessions, - more than 120 speakers from around the world, - 4 brilliant keynotes, - 2 exciting lightning talk blocks, - 4 all-day tracks, with a whole track dedicated to data science topics, - a poster track, - a virtual social event, - an after party, - and lots of socializing on our conference platform. Conference tickets are available on our registration page. We hope to see lots of you at the conference from July 23-26. Rest assured that we’ll make this a great event again — even within the limitations of running the conference online. https://ep2020.europython.eu/registration/buy-tickets/ Help spread the word Please help us spread this message by sharing it on your social networks as widely as possible. Thank you ! Link to the blog post: https://blog.europython.eu/post/622517324925321216/europython-2020-our-keynotes Tweet: https://twitter.com/europython/status/1278608198870749184 Thanks, -- EuroPython 2020 Team https://ep2020.europython.eu/ https://www.europython-society.org/ -- https://mail.python.org/mailman/listinfo/python-list
Re: trying to improve my knn algorithm
[email protected] wrote: > This is another account but I am the op. Why do you mean normalize? Sorry > I’m new at this. Take three texts containing the words covid, vaccine, program, python Some preparatory imports because I'm using numpy: >>> from numpy import array >>> from numpy.linalg import norm The texts as vectors, the first entry representing "covid" etc.: >>> text1 = array([1, 1, 0, 0]) # a short text about health >>> text2 = array([5, 5, 0, 0]) # a longer text about health >>> text3 = array([0, 0, 1, 1]) # a short text about programming in Python Using your distance algorithm you get >>> norm(text1-text2) 5.6568542494923806 >>> norm(text1-text3) 2.0 The two short texts have greater similarity than the texts about the same topic! You get a better result if you divide by the total number of words, i. e. replace absolute word count with relative word frequency >>> text1/text1.sum() array([ 0.5, 0.5, 0. , 0. ]) >>> norm(text1/text1.sum() - text2/text2.sum()) 0.0 >>> norm(text1/text1.sum() - text3/text3.sum()) 1.0 or normalize the vector length: >>> norm(text1/norm(text1) - text2/norm(text2)) 0.0 >>> norm(text1/norm(text1) - text3/norm(text3)) 1.4142135623730949 -- https://mail.python.org/mailman/listinfo/python-list
RE: trying to improve my knn algorithm
Hi, I think you sent this to the wrong person. [cid:storage_emulated_0__EmailTempImage_5_TempSignature_signature_20200630_205218_jpg_1593543161247] [cid:storage_emulated_0__EmailTempImage_5_TempSignature_signature_20200630_205334_jpg_1593543223538] [cid:storage_emulated_0__EmailTempImage_5_TempSignature_signature_20200630_205420_jpg_1593543265258][cid:storage_emulated_0__EmailTempImage_5_TempSignature_signature_20200630_205456_jpg_1593543303538] Kind Regards, Raine Pretorius [cid:storage_emulated_0__EmailTempImage_5_TempSignature_signature_20200630_205658_jpg_1593543438262] Original message From: Peter Otten <[email protected]> Date: 2020/07/02 11:09 (GMT+02:00) To: [email protected] Subject: Re: trying to improve my knn algorithm [email protected] wrote: > This is another account but I am the op. Why do you mean normalize? Sorry > I’m new at this. Take three texts containing the words covid, vaccine, program, python Some preparatory imports because I'm using numpy: >>> from numpy import array >>> from numpy.linalg import norm The texts as vectors, the first entry representing "covid" etc.: >>> text1 = array([1, 1, 0, 0]) # a short text about health >>> text2 = array([5, 5, 0, 0]) # a longer text about health >>> text3 = array([0, 0, 1, 1]) # a short text about programming in Python Using your distance algorithm you get >>> norm(text1-text2) 5.6568542494923806 >>> norm(text1-text3) 2.0 The two short texts have greater similarity than the texts about the same topic! You get a better result if you divide by the total number of words, i. e. replace absolute word count with relative word frequency >>> text1/text1.sum() array([ 0.5, 0.5, 0. , 0. ]) >>> norm(text1/text1.sum() - text2/text2.sum()) 0.0 >>> norm(text1/text1.sum() - text3/text3.sum()) 1.0 or normalize the vector length: >>> norm(text1/norm(text1) - text2/norm(text2)) 0.0 >>> norm(text1/norm(text1) - text3/norm(text3)) 1.4142135623730949 -- https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Formal Question to Steering Council (re recent PEP8 changes)
We've had the requested 24 hour cooling off, and I don't imagine anyone is surprised that the situation remains unchanged. The commit message that caused the controversy is still in the PEP repository, and is still controversial. Whether you think it's the best thing since the last best thing or the biggest load of bollocks since the last biggest load of bollocks is irrelevant. It's there, it espouses a political stance, and by implication the Steering Council support it. Since explicit is better than implicit :-), I would like to formally ask the Steering Council to answer the following questions. 1. Does the Steering Council think political statements have any place in the Python repositories? 2. If so, for the avoidance of doubt does the Steering Council support the statements in commit 0c6427d? (https://github.com/python/peps/commit/0c6427dcec1e98ca0bd46a876a7219ee4a9347f4) 3. If not, what do they intend to do about the above commit? If the answer to question 1 is a qualified yes or no, both follow-up questions apply. If the answer to question 1 is a prevarication, non-answer or silence, people will still draw their own conclusions. I mention this merely to reinforce the idea that these things are still answers as well as hostages to fortune. -- Rhodri James *-* Kynesim Ltd -- https://mail.python.org/mailman/listinfo/python-list
Re: Formal Question to Steering Council (re recent PEP8 changes)
On 07/02/2020 06:39 AM, Rhodri James wrote: We've had the requested 24 hour cooling off, and I don't imagine anyone is surprised that the situation remains unchanged. The commit message that caused the controversy is still in the PEP repository, and is still controversial. Whether you think it's the best thing since the last best thing or the biggest load of bollocks since the last biggest load of bollocks is irrelevant. It's there, it espouses a political stance, and by implication the Steering Council support it. Since explicit is better than implicit :-), I would like to formally ask the Steering Council to answer the following questions. An issue asking basically the same thing has been created: https://github.com/python/steering-council/issues/31 -- ~Ethan~ -- https://mail.python.org/mailman/listinfo/python-list
Re: Formal Question to Steering Council (re recent PEP8 changes)
Rhodri James wrote at 2020-7-2 14:39 +0100: >We've had the requested 24 hour cooling off, and I don't imagine anyone >is surprised that the situation remains unchanged. The commit message >that caused the controversy is still in the PEP repository, and is still >controversial. Whether you think it's the best thing since the last >best thing or the biggest load of bollocks since the last biggest load >of bollocks is irrelevant. It's there, it espouses a political stance, >and by implication the Steering Council support it. > >Since explicit is better than implicit :-), I would like to formally ask >the Steering Council to answer the following questions. I am no member of the Council. Thus, your questions are not directed to me. **BUT** you made your questions public and thus you are likely prepared to receive public comments. The commit message tries to provide the motivation for the change. In my view, it is good to document change motivations and a commit message is not a bad place for that. In the replaced sentence `When writing English, follow Strunk and White` I interpret "Strunk and White" as a reference to some document containing rules for readable English and "Strunk and White" are likely the authors of this document. I do not associate "White" with "white" in contrast to "black" (or some other colour). However, I do not know this document nor "Strunk and White". Thus, the PEP text should get improved. If it is refers to a standard, it should be be an online standard and the PEP should include its URL. Otherwise, non-english people are indeed at a disadvantage. In contrast, The replacement is well understandable and applicable to all languages. Thus, in my view, the change is really an improvement. One could motivate it differently, however. -- https://mail.python.org/mailman/listinfo/python-list
Re: Formal Question to Steering Council (re recent PEP8 changes)
On 02/07/2020 18:11, Dieter Maurer wrote: I am no member of the Council. Thus, your questions are not directed to me. **BUT** you made your questions public and thus you are likely prepared to receive public comments. Fortunately you don't answer any of the questions, so I don't need to have an opinion on that :-) The commit message tries to provide the motivation for the change. In my view, it is good to document change motivations and a commit message is not a bad place for that. True. However, the motivation as appeared in the discussions was (approximately) that many people, especially those whose first language is not English, find being given a list of writing guidelines like Strunk and White's "The Elements of Style" intimidating. That's fair enough, though a bit more consideration suggests that many people have exactly the opposite problem. The wording could be amended to reassure both, and I've been contemplating doing so. The political diatribe about the linguistic contribution to white supremacy of standardized English appeared nowhere in the discussion. Had it done so, I suspect Keala would have realised quite quickly that using it would be (and has been) controversial and divisive, the exact opposite of her stated intentions. All of which is quite beside the point for the questions I raised. As I said, it doesn't matter whether you agree with that political opinion raised, disagree with it, or do not give a monkey's, should _any_ political opinion be in the repo? -- Rhodri James *-* Kynesim Ltd -- https://mail.python.org/mailman/listinfo/python-list
Re: Formal Question to Steering Council (re recent PEP8 changes)
On 7/2/20 12:04 PM, Rhodri James wrote: > On 02/07/2020 18:11, Dieter Maurer wrote: >> I am no member of the Council. Thus, your questions are not directed >> to me. **BUT** you made your questions public and thus you are >> likely prepared to receive public comments. > > Fortunately you don't answer any of the questions, so I don't need to > have an opinion on that :-) > >> The commit message tries to provide the motivation for >> the change. In my view, it is good to document change motivations >> and a commit message is not a bad place for that. > > True. However, the motivation as appeared in the discussions was > (approximately) that many people, especially those whose first language > is not English, find being given a list of writing guidelines like > Strunk and White's "The Elements of Style" intimidating. That's fair > enough, though a bit more consideration suggests that many people have > exactly the opposite problem. The wording could be amended to reassure > both, and I've been contemplating doing so. Indeed, without weighing in on this case itself, the purpose of calling out a "standard langauge" for formal documents is to remove sources of ambiguity, not to promote one viewpoint or another: not sure how to express something? Let's see if the style manual has anything to guide me. Not to intimidate someone about having set an impossible bar for writing. So if there's a way to express that, I'm sure everybody would be happier! -- https://mail.python.org/mailman/listinfo/python-list
Re: Formal Question to Steering Council (re recent PEP8 changes)
On 7/2/20 11:11 AM, Dieter Maurer wrote: > In the replaced sentence > `When writing English, follow Strunk and White` > I interpret "Strunk and White" as a reference to some > document containing rules for readable English and "Strunk and White" > are likely the authors of this document. I do not associate "White" > with "white" in contrast to "black" (or some other colour). > However, I do not know this document nor "Strunk and White". Thus, > the PEP text should get improved. If it is refers to a standard, > it should be be an online standard and the PEP should include its URL. > Otherwise, non-english people are indeed at a disadvantage. Yes Strunk and White is a well-known book on writing style. That's the names of the authors. William Strunk and EB White. https://en.wikipedia.org/wiki/The_Elements_of_Style > In contrast, The replacement is well understandable and applicable > to all languages. Agreed. She just needs to fix her commit message to remove the sentence about the relics of white supremacy. The fact she would conflate an author's name with some kind of race-related thing is a bit embarrassing, frankly. > Thus, in my view, the change is really an improvement. > One could motivate it differently, however. -- https://mail.python.org/mailman/listinfo/python-list
Re: FW: Pycharm Won't Do Long Underscore
Il 30/06/2020 23:46, Joe Pfeiffer ha scritto: > "Peter J. Holzer" writes: > >> On 2020-06-24 15:33:16 -0600, Joe Pfeiffer wrote: >>> One other note -- while you may want various good-looking fonts with >>> ligatures in other domains, for writing code a monospace font with no >>> ligatures lets you see exactly what's there and saves a host of >>> problems. My personal favorite for these purposes is called "Terminus >>> Regular", but which specific one you pick is much less important than >>> that you use one. >> >> I agree. Although there are some fonts with special ligatures for >> programming. I have never used one, but that seems like an interesting >> concept. > > I've never heard of that before. I'd be curious to try one. > I've been using this one, and I like it: https://github.com/tonsky/FiraCode https://www.fontsquirrel.com/fonts/fira-code Works well with PyCharm. -- https://mail.python.org/mailman/listinfo/python-list
PEP 622
Why are OR patterns going to use the bitwise operator instead of logical or operator? https://www.python.org/dev/peps/pep-0622/#combining-multiple-patterns-or-patterns -Steve -- https://mail.python.org/mailman/listinfo/python-list
Re: Formal Question to Steering Council (re recent PEP8 changes)
On 2020-07-02, Michael Torrie wrote: > Agreed. She just needs to fix her commit message to remove the sentence > about the relics of white supremacy. The fact she would conflate an > author's name with some kind of race-related thing is a bit > embarrassing, frankly. She didn't - you did. -- https://mail.python.org/mailman/listinfo/python-list
Re: PEP 622
On Fri, Jul 3, 2020 at 7:48 AM Stephen Carboni wrote: > > Why are OR patterns going to use the bitwise operator instead of > logical or operator? > > https://www.python.org/dev/peps/pep-0622/#combining-multiple-patterns-or-patterns > Keep reading :) https://www.python.org/dev/peps/pep-0622/#use-some-other-syntax-instead-of-for-or-patterns ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Formal Question to Steering Council (re recent PEP8 changes)
On 07/02/2020 12:14 PM, Michael Torrie wrote: The fact she would conflate an author's name with some kind of race-related thing is a bit embarrassing, frankly. It seems she has studied literary and English history, at least as related to the 20th century, so I don't think any name conflation is going on. I have asked for links that would support her view as expressed in the commit message, but haven't yet seen any. -- ~Ethan~ -- https://mail.python.org/mailman/listinfo/python-list
Re: Formal Question to Steering Council (re recent PEP8 changes)
On 7/2/20 1:26 PM, Jon Ribbens via Python-list wrote: > On 2020-07-02, Michael Torrie wrote: >> Agreed. She just needs to fix her commit message to remove the sentence >> about the relics of white supremacy. The fact she would conflate an >> author's name with some kind of race-related thing is a bit >> embarrassing, frankly. > > She didn't - you did. Come again? I can see no other link in the verbage with the "relics of white supremacy" that she referred to. If there are other links, they should be included in the commit message. I agree with Rhodri that an explanation would be interesting. Far be it from me to demand one. So whatever. -- https://mail.python.org/mailman/listinfo/python-list
Re: FW: Pycharm Won't Do Long Underscore
On 7/2/20 2:55 PM, Danilo Coccia wrote: > Il 30/06/2020 23:46, Joe Pfeiffer ha scritto: >> "Peter J. Holzer" writes: >>> I agree. Although there are some fonts with special ligatures for >>> programming. I have never used one, but that seems like an interesting >>> concept. >> >> I've never heard of that before. I'd be curious to try one. >> > > I've been using this one, and I like it: > https://github.com/tonsky/FiraCode > https://www.fontsquirrel.com/fonts/fira-code > > Works well with PyCharm. Hmm. That is... interesting. I'm not at all sure how I feel about that. On the one hand it partly appeals, but on the other hand it quite repulses me. I don't find the FireCode samples any easier to read than a normal font. In fact I find it slightly more difficult to read, since my brain is not used to looking for those symbols. Hmmm. Yeah I dunno about this one! Very interesting. Thanks for sharing it. I tried it, and it's definitely not for me! -- https://mail.python.org/mailman/listinfo/python-list
Re: Formal Question to Steering Council (re recent PEP8 changes)
On Thu, Jul 2, 2020, at 18:29, Michael Torrie wrote: > Come again? I can see no other link in the verbage with the "relics of > white supremacy" that she referred to. If there are other links, they > should be included in the commit message. I agree with Rhodri that an > explanation would be interesting. Far be it from me to demand one. So > whatever. It's possible that this wasn't explained clearly enough in the commit message itself (though I would argue it was definitely adequately explained in the ensuing on-list discussion, and wonder how much of that discussion you've actually read), but the point is that the *whole idea* of "standard English" is tied to white supremacy, not any particular standard whether via its authors or otherwise. -- https://mail.python.org/mailman/listinfo/python-list
Re: Formal Question to Steering Council (re recent PEP8 changes)
> On Jul 2, 2020, at 5:48 PM, Random832 wrote: > > but the point is that the *whole idea* of "standard English" is tied to white > supremacy Bunkum. It is racist to claim that standards are against people, when their purpose to to make the written word understood by all who read it, as opposed to having to understand all dialects. There are numerous “white” dialects whose words and grammars are not included in those standards. Bev in TX -- https://mail.python.org/mailman/listinfo/python-list
Re: Formal Question to Steering Council (re recent PEP8 changes)
On 7/2/20 4:46 PM, Random832 wrote: > It's possible that this wasn't explained clearly enough in the commit > message itself (though I would argue it was definitely adequately > explained in the ensuing on-list discussion, and wonder how much of > that discussion you've actually read), but the point is that the > *whole idea* of "standard English" is tied to white supremacy, not > any particular standard whether via its authors or otherwise. Good to know. Nothing at all was explained in the commit message justifying that particular sentence, leaving one unfamiliar with the background to wonder what she was referring to. I definitely agree the words "standard English" are pretty meaningless to would-be python developers anyway and the new phrase in the PEP 8 is much better. -- https://mail.python.org/mailman/listinfo/python-list
