> . In fact, I'd be > pretty certain that something like this probably already exists on > PyPI, but I wouldn't know how to find it.
It's supported with several syntaxes in macropy ( https://pypi.org/project/MacroPy/) but I remember seeing it in a more serious (for lack of a better term) package too, I just can't remember which one. E On Fri, 26 Nov 2021 at 19:41, Paul Moore <p.f.mo...@gmail.com> wrote: > On Fri, 26 Nov 2021 at 14:39, Raimi bin Karim <raimi.bka...@gmail.com> > wrote: > > > So this is more of a heartfelt note rather than an objective one — I > would love > > my fellow Python programmers to be exposed to this mental model, and that > > could only be done by implementing it in the standard library. > > I'm somewhat ambivalent about this pattern. Sometimes I find it > readable and natural, other times it doesn't fit my intuition for the > problem domain. I do agree that helping people gain familiarity with > different approaches and ways of expressing a computation, is a good > thing. > > I get your point that putting this functionality in a 3rd party > library might not "expose" it as much as you want. In fact, I'd be > pretty certain that something like this probably already exists on > PyPI, but I wouldn't know how to find it. However, just because that > doesn't provide the exposure you're suggesting, doesn't mean that it > "could only be done by implementing it in the standard library". This > isn't a technical problem, it's much more of a teaching and > evangelisation issue. Building a library and promoting it via blogs, > social media, demonstrations, etc, is a much better way of getting > people interested. Showcasing the approach in an application that lots > of people use is another (Pandas, for example, shows off the "fluent" > style of chained method calls, which some people love and some hate, > that's very similar to your proposal here). It's a lot of work, > though, and not the type of work that a programmer is necessarily good > at. Many great libraries are relatively obscure, because the author > doesn't have the skills/interest/luck to promote them. > > What you *do* get from inclusion in the stdlib is a certain amount of > "free publicity" - the "What's new" notices, people discussing new > features, the general sense of "official sanction" that comes from > stdlib inclusion. Those are all useful in promoting a new style - but > you don't get them just by asking, the feature needs to qualify for > the stdlib *first*, and the promotion is more a "free benefit" after > the fact. And in any case, as others have mentioned, even being in the > stdlib isn't guaranteed visibility - there's lots of stuff in the > stdlib that gets overlooked and/or ignored. > > Sorry - I don't have a good answer for you here. But I doubt you'll > find anyone who would be willing to help you champion this for the > stdlib. > > Paul > _______________________________________________ > Python-ideas mailing list -- python-ideas@python.org > To unsubscribe send an email to python-ideas-le...@python.org > https://mail.python.org/mailman3/lists/python-ideas.python.org/ > Message archived at > https://mail.python.org/archives/list/python-ideas@python.org/message/WRSCVNGAS6JALJY56ZE7EU634V7DU73G/ > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/AZIMUGG6SZMLBRVOBXXO2BKERKWHQXEC/ Code of Conduct: http://python.org/psf/codeofconduct/
