Mailman 3 February 2020 - Edu-sig

Part-time opportunities for Python instructors
by Merav Yuravlivker 07 May '24

07 May '24

Hi there, My name is Merav Yuravlivker, and I'm the CEO of Data Society - we deliver data science academies to Fortune 500 companies, government agencies, and other international organizations. We're currently looking for part-time Python instructors and TAs, and my friend Jackie Kazil recommended I reach out to you and your list serv. All of these opportunities can be available for people who are employed full-time, professors, or grad students. We pay well and provide all the materials for the instructor, as well as instructor training and support. If possible, would you please be able to share the following blurb? Please let me know if there is anything else you need from me. Much appreciated! Best, Merav --- Data Society, a fast-growing data science training company, is looking for awesome Python instructors and TAs! We deliver data academies to Fortune 500 companies, government agencies, and international organizations. All of our content is built in-house by an expert team of data scientists and instructional designers, so you can focus on what you do best - teach professionals how to find new insights and make their jobs easier. We currently have a few openings for TAs, as well as part-time instructors - all of these opportunities can be available for people who are employed full-time, professors, or grad students. We pay competitively, have a great support team, and provide amazing opportunities for additional projects if you're interested. To learn more, please visit our page for current opportunities <https://t.sidekickopen10.com/s2t/c/5/f18dQhb0S7lM8dDMPbW2n0x6l2B9nMJN7t5X-F…>, or simply reach out to Merav at merav(a)datasociety.com. -- Schedule a time to meet <https://t.sidekickopen10.com/s1t/c/5/f18dQhb0S7lM8dDMPbW2n0x6l2B9nMJN7t5X-F…> Merav Yuravlivker Data Society, Chief Executive Officer and Co-founder 777 6th Street NW, 11th Floor Washington, D.C., 20001 Enterprise: solutions.datasociety.com Consumer: datasociety.com

6 5

a short essay about programming
by kirby urner 08 Dec '22

08 Dec '22

A common "error" (not too serious) that I see in beginning Python (and no doubt other languages, but Python is the one I'm teaching), is having a while condition that appears to put a lid on things, but then the flow all leaks away through break statements, such that the "front door" condition is never revisited. while guess != secret: guess = int(input("Guess?: ") if guess == secret: print("You guessed it!") break else: print("Nope, try again...") What's messed up about the above code is you never really go back to the top in the case where you'd get to leave. Rather, you exit by the back door, through break. So in that case, wouldn't have been simpler and more elegant, even more "correct" (dare I say it) to have gone: while True: # no ifs ands or buts guess = int(input("Guess?: ") if guess == secret: print("You guessed it!") break else: print("Nope, try again...") I see lots of heads nodding, and that could be the end of the matter, but then a next question arises: wouldn't this also be a more correct solution?: while guess != secret: guess = int(input("Guess?: ") if guess == secret: print("You guessed it!") continue # instead of break else: print("Nope, try again...") We're back to having a variable while condition, not a boolean constant, but this time we actually exit by means of it, thanks to continue or... while guess != secret: guess = int(input("Guess?: ") if guess == secret: print("You guessed it!") else: print("Nope, try again...") ... thanks to no continue. This last one is getting a thumbs up, but then I'd pause here and say "continue" can be easier on the eyes. It's unambiguous where it takes you, in contrast to having to scan on down the gauntlet, looking for possibly other open doors. "What happens next" should not require scanning ahead too far. Help us not to get lost. Be a civic-minded coder. I'm thinking of a programming style that advises two things: (a) if you use a while condition that's variable, that's expected to change, then your goal should be to always exit because of that, i.e. that should be your only exit point. Even if some other criterion suggests exiting, you have the option to flip that "lid" at the top, to crack that front door, and bounce the ball out. (b) which is why 'continue' is your friend. You are showing the user where your 'break' statements are, except you don't use "break" statements, as you've given a non-constant condition, and your aim is to make that your ONLY exit point. In short: never use break to exit a while loop unless your condition is while True. Instead, always flip the condition and exit through the font door. However, as soon as I make that rule I can think of good reasons to break it. The other programmers in the room are shaking their heads. Won't we lose information, needed elsewhere in the program, if we "artificially" force a True condition to False. Aren't we, in effect, lying? That concern could be addressed. Keep all the info true, just treat the "lid condition" (it "keeps a lid on it") as a flag. Go ahead and remember the user's guess. allowed = 5 tries = 1 exit = False while not exit: # no other way out guess = int(input("Guess?: ") if guess == secret: print("You guessed it!") exit = True # instead of break continue print("Nope, try again...") tries += 1 if tries == allowed: print("You've maxed out") exit = True continue I think we all understand the main issue: writing reader-friendly code, and rules for doing so. There's something comforting about approaching a while loop and knowing its not a leaky sieve, riddled with back doors, maybe even an exit( ) time bomb. But in the recursion world we want a minimum of two exits usually: when another round is called for versus when we've "hit bottom". Can we have it both ways? Conclusions: Lets not be too hasty with rules of thumb and: Lets keep the reader in mind when writing code. Just because the interpreter knows to compute the flow unambiguously, doesn't mean all ways of writing it are equally reader-friendly. What may seem a gratuitous gesture, an unnecessary flourish, may actually promote reader comprehension of your code, and that should be a goal as much as satisfying the interpreter. Kirby

8 17

MineCraft with Python
by Jurgis Pralgauskis 04 Dec '22

04 Dec '22

Hi, intro: many kids like MineCraft :) probably you know/heared of MineCraft Pi https://www.raspberrypi.org/learning/getting-started-with-minecraft-pi/ But there seems to be Py for real MC http://coderdojotc.readthedocs.io/projects/python-minecraft/en/latest/ http://www.instructables.com/id/Python-coding-for-Minecraft/ PS.: a nice article (from js4MC world) https://github.com/walterhiggins/ScriptCraft/blob/master/docs/YoungPersonsG… -- Jurgis Pralgauskis tel: 8-616 77613; Don't worry, be happy and make things better ;) http://galvosukykla.lt

6 6

#1 new book in Children's Computer Programming
by Kent Tong 26 Feb '20

26 Feb '20

Hi, I am glad that my book is currently the #1 new book in the Children's Computer Programming category on Amazon. Please take a look ( https://www.amazon.com/Yes-Kids-can-learn-Python-ebook/dp/B084CY2L43/ref=sr…) to see if you may make use of it at your school. I will be more than happy to provide any assistance that you need :-) [image: image.png] -- Kent Tong IT author and consultant, child education coach

2 2

Python 3.8 breaks backward compatibility with math.factorial(Decimal(int))
by kirby urner 18 Feb '20

18 Feb '20

Now you'll need to use math.factorial(int(Decimal)) or write your own factorial function. The storyline: Apropos of recent threads experimenting with high precision (arbitrary precision) numbers as a way to promote interest in "pure math" applications using Python, I discovered this morning that my Ramanujan Convergence script on repl.it <https://repl.it/@kurner/computepi> was broken all of a sudden (after working before), and set out to discover why. Answer: in Python 3.8, to which repl.it has newly upgraded, math.factorial no longer accepts Decimal type numbers, even if they're integral (integers). You can read the discussion here: https://bugs.python.org/issue33083 Here's the line of code that broke, and was fixed with explicit castings to int. term = (fact(int(c1*i))*(c2 + c3*i))/(pow(fact(int(i)),4)*pow(c4,4*i)) By the time of the final division, the numerator and denominator have been coerced back into Decimals and so will divide with the expected precision (set by the context): Where: ``` c1 = Decimal(4) c2 = Decimal(1103) c3 = Decimal(26390) c4 = Decimal(396) c5 = Decimal(9801) ``` For more context: https://github.com/4dsolutions/Python5/blob/master/Pi%20Day%20Fun.ipynb (I'm updating it now...) Kirby

1 0

Re: mailman 3: howzitgoin?
by Naomi Ceder 07 Feb '20

07 Feb '20

So it looks like both restructured text and markdown formatting is supported.... how clever is that? Hope this answers your question, Kirby. Cheers, Naomi -- Naomi Ceder @NaomiCeder • https://www.naomiceder.tech https://www.manning.com/books/the-quick-python-book-third-edition

1 0

mailman 3: howzitgoin?
by kirby urner 07 Feb '20

07 Feb '20

Looking back in the archive: https://mail.python.org/archives/list/edu-sig@python.org/message/WE5WEZIMTZ… The rendering I get turns the double-star of Python exponentiation into some kind of boldfacing, like we're in a wiki or using markdown or something. The attachment shows the original content, but requires a download to see. Is there a button-click way to redisplay / re-render a post in original format? Nor is my Python source code showing up with indenting. Do I need to format in some new wiki way? What default settings do we have, to restore Python-friendliness, I wonder. Kirby Urner edu-sig listowner

2 3

My e-book to teach kids Python is free within the next 24 hours on Amazon
by Kent Tong 04 Feb '20

04 Feb '20

Hi, If you're interested, you can get it for free at: https://www.amazon.com/Yes-Kids-can-learn-Python-ebook/dp/B084CY2L43/ref=sr… Best regards, -- Kent Tong IT author and consultant, child education coach

2 1

arbitrary precision computing in K-12
by kirby urner 03 Feb '20

03 Feb '20

A lot of our archived debates centered around how we might redesign (reform) the curriculum in light of computer languages, Python in particular. What I'm coming to lately is emphasizing arbitrary precision e.g. pi to literally a thousand places, as an especially attractive feature of computers in general. Mere calculators don't usually do arbitrary precision (I remember one Casio (?) with a scrolled display), but seem more reliable in giving the expected grade school results vs. answers we might get from using floating points (IEEE 754), which bring their own form of disillusionment. In other words, in going from a basic math topic, such as irrational numbers, to computers, why not emphasize the extrapolation of our algorithms to large numbers of decimal digits? Lets compute Phi as (1 + sqrt(5))/2 to hundreds of digits and check published sources (such multi-digit comparisons might mean converting to strings). We've done stuff like that around pi here on edu-sig, computing from algorithms (one of Ramanujan's in particular). These arbitrary precision numbers may not have much use in scientific and engineering applications (because nothing gets measured to that degree of precision) but I'm talking about bridging from math, so-called "pure math" in particular. My approach of late has been to use geometric objects (volumes, polyhedrons) and check that our computations may be exact to several hundred decimal points thanks to Python's Decimal. I also use the 3rd party gmpy2 library. Here's an essay on Medium if you'd like to read more: https://medium.com/@kirbyurner/calculator-of-tomorrow-using-arbitrary-preci… Kirby

4 12