steering-council VS full-speed-python

GVR called it a fork two weeks ago in his justification for not accepting it [1]. If that surprises you, the backstory is summarized pretty well in the article [2] and FAQ [3].

I'm really not trying to be secretive. We can debate whatever you want, but we have to at least acknowledge CPython's stated position.

[1] https://github.com/python/steering-council/issues/188#issuec...

[2] https://www.artima.com/weblogs/viewpost.jsp?thread=214235

[3] https://docs.python.org/3/faq/library.html#can-t-we-get-rid-...

Thanks for reviewing the PEP. The PEP was posted five months ago, and it has been 20 months since an end-to-end working implementation (that works with a large number of extensions) was discussed on python-dev. I appreciate everyone who has taken the time to review the PEP and offer comments and suggestions.

You wrote that the Steering Council's decision does not mean "no," but the steering council has not set a bar for acceptance, stated what evidence is actually needed, nor said when a final decision will be made. Given the expressed demand for PEP 703, it makes sense to me for the steering committee to develop a timeline for identifying the factors it may need to consider and for determining the steps that would be required for the change to happen smoothly.

Without these timelines and milestones in place, I would like to explain that the effect of the Steering Council's answer is a "no" in practice. I have been funded to work on this for the past few years with the milestone of submitting the PEP along with a comprehensive implementation to convince the Python community. Without specific concerns or a clear bar for acceptance, I (and my funding organization) will have to treat the current decision-in-limbo as a “no” and will be unable to pursue the PEP further.

Github Link: https://github.com/python/steering-council/issues/188#issuec...

Hmm, likely because it was already submitted to the steering council since April and because the addition is relatively trivial (at runtime, it's almost a no-op).

If you're learning Python, and know other programming languages, I have this online ebook [1] that I use with my students so that they learn Python fast enough so that I can teach them about socket programming.

Basically, in each chapter I give a small detailed introduction to the topic and then students do some exercises to solidify things.

[1] https://github.com/joaoventura/full-speed-python

SEEKING FREELANCE WORK

I'm available for Python and Django freelance work, if it's interesting enough. I've 10+ years of professional experience working with that stack. You can check some of my projects at [1] and look at some of my code at [2] and [3].

I'm also a part-time CS Professor (I have a CS PhD - AI - TextMining), so I'm also available for tutoring students 1-1 (or small groups). Topics can include anything from CS curricula, but I have lots of experience introducing people to programming (I have a Python ebook with exercises - fullspeedpython [4]), and building web apps either in Python or Java (intro to programming, databases, networking, html+css, webframeworks, webservices => web apps). If you're new to CS and programming and you're self-learning, I can help you navigate what's important, what's irrelevant and provide you with some guidance.

Giving that I see thousands and thousands of code every semester, I'm also available for doing code reviews or helping with best practices for individuals and teams.

My current rate is 80€-100€/hour.

[1] https://joaoventura.net/projects/

[2] https://github.com/joaoventura/

[3] https://github.com/flatangle/flatlib

[4] https://github.com/joaoventura/full-speed-python

I’m in the initial phase of structuring a book that aims to teach some simple algorithms and data structures using Python. The idea is that the reader should do the (guided) exercises to learn how to build those data structures. It’s basically “learn by doing”.

For instance, to teach what a stack is I’ll explain the basic idea of a stack, then provide a base class and the reader must implement each method (init, push, pop, peek, etc) given the requirements and intended results of each functionality.

I have a learn by doing ebook about Python (https://github.com/joaoventura/full-speed-python), so it’s like a follow-up to that one. Don’t know if people are interested though..

Cool list! @pamoroso, if you read this comment, I've submitted an issue on the repo to add my own ebook (full-speed python).

If someone stumbles on this on HN, here's the link to the repo [1] and releases [2]. It's basically a simple ebook where each chapter shows a little bit of what you can do with something (numbers, strings, lists, dicts, modules, etc.) and then the reader solves the asked exercises. I use this for my students who already know how to program (BSc and MSc) to get up to speed with Python, so that we can go learn sockets, http protocols, web frameworks, etc..

[1] https://github.com/joaoventura/full-speed-python/

[2] https://github.com/joaoventura/full-speed-python/releases/