[Python-Dev] Fixing unbuffered output on Windows
Hi all, I've created a pull request some time ago to fix https://bugs.python.org/issue42044 ( https://github.com/python/cpython/pull/26678). I know python devs are pretty busy, but I'd really appreciate it if someone could take a look at it (as I *think* it's a simple fix). Thanks, Fabio ___ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/5HM65EF4NA5SR3NGJDMXUZMJFCL6FTJK/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: Is the Python review process flawed?
On Fri, Jul 2, 2021 at 12:47 AM wrote: > Okay so I just code a little bit and I used the multiprocessing module but > my code didn't work and I found the solution on Stack Overflow and it > turned out to be not my mistake (which has never happened before I think). > Instead I found out it's a bug in Python and the issue on Github was linked > so I opened it and I was surprised to see what's going on "behind the > scenes". > > Yes I have basically no experience in maintaining any big project. So when > you're saying "You don't know what it's like and therefore your complaint > doesn't make sense" then you're not wrong and I just have to believe you. > But I think this is a dangerous argument because it could also be used to > shut up anything and anybody. (I'm not saying this is the case here.) > Therefore, this argument should rarely be used in my opinion. From an > outsider's perspective it just looks really weird that a bugfix from 2017 > hasn't become a priority to get merged, like the process is flawed. That's > all. I didn't mean to attack any one of you. I want to make that clear > because it feels like some of you got kinda defensive about it. > > I don't think anyone felt attacked. The hard-working devs are merely trying to explain the facts of life, and if exasperation occasionally creeps in that's probably because this is far from the first time this issue has been raised here. (You'll note I refer to the core devs in the third person, since I am not one of them and neither do I speak for them, I am merely recording my observations). "There's been quite a bit of discussion on both of them" - None of the > discussions left any questions unanswered. Except for the question of when > the pull request will get merged. > > "Merging something is also a responsibility to whoever does it" - And it's > also a responsibility to fix bugs, no? I don't get why you're so afraid of > (maybe!) introducing a new bug when there already (certainly!) is a bug. > > Whose "responsibility" do you think it should be to fix bugs? Who do you think should set priorities to determine which work is done first. Few core developers are paid to work on Python, and even those that are (until the PSF's developer is appointed) might expect to have their overall priorities set by their employer. As a consumer of their work who's made little contribution to the language I don't personally feel that I have much right to dictate how devs spend their time. I'm just glad so many of them do. The fact is that for any community-run open source project the only reliable way to ensure PRs get merged is to acquire commit rights and do it yourself. It's by no means ideal, but that's the current reality for Python. "Oops. I'm really sorry for giving false hopes, then, because I don't think > I'm motivated to review this PR. I'm not really maintaining multiprocessing > these days, anymore" - No worries dude. This not about one person or one > bug. I'm sorry that the issue that I stumbled upon turned out to be one > where you said you'd put it on your list. > > "What if that one line change is even more wrong than before?" - Yes of > course there's a risk. Just like there was a risk when you merged the > original code which contained the bug, right?! At some point you have to > say yes that looks okay let's merge it, even though there is a slight > chance it could contain a mistake. And it is not obvious to me (and many > other people who commented in those github threads) what else would > possibly be needed. After all, there are currently actual people who are > affected by the bug - and you're only talking about hypothetical people > being affected by a possibly wrong bugfix. > > Let's assume that it takes an hour to properly review and merge a PR. If someone only has five hours a week to work on Python they are hardly going to consider spending 20% of their available time tht week on sometthing unrelted to the work they've been doint of rk > "When I got the shutil.which feature merged, the PR had been open for I > believe 11 years" - Totally different topic. I explicitly said in my > initial message, that I'm talking about a bugfix, not a new feature. > > "If you would like more value out of it or to speed up the process, you > can provide your own reviews." - Seriously? I can't help but feel like that > comment sounds kinda arrogant. I hope I'm misunderstanding you. Look at > that link and Stack Overflow post again how many people commented and voted > that the patch fixed their issues. How many more people do you want? > > It isn't a matter of summoning the desire, it's a matter of allocating time. > "*maintainer attention* is actually the scarcest resource in many open > source projects, and Python is no exception." - Then get more people to do > this? Don't tell me Python isn't big enough to find some companies or funds > to sponsor a few people to work the dreaded reviewer job a few hours a > week? Or let more amateur coders rev
[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2021-06-25 - 2021-07-02) Python tracker at https://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open7398 (-12) closed 48891 (+57) total 56289 (+45) Open issues with patches: 2951 Issues opened (28) == #23041: csv needs more quoting rules https://bugs.python.org/issue23041 reopened by skip.montanaro #41180: marshal load bypass code.__new__ audit event https://bugs.python.org/issue41180 reopened by steve.dower #44511: Improve the bytecode for mapping patterns https://bugs.python.org/issue44511 opened by brandtbucher #44512: csv.DictWriter: inconsistency in handling of extrasaction arg https://bugs.python.org/issue44512 opened by andrei.avk #44514: configparser.rst & bz2.rst leave temp files after 'make doctes https://bugs.python.org/issue44514 opened by kfollstad #44515: contextlib test incompatibility with non-refcounted GC https://bugs.python.org/issue44515 opened by ncoghlan #44516: Update bundled pip to 21.1.3 https://bugs.python.org/issue44516 opened by sbidoul #44517: test__xxsubinterpreters: AMD64 Fedora Stable 3.x buildbot abor https://bugs.python.org/issue44517 opened by erlendaasland #44518: Finalization of non-exhausted asynchronous generators is defer https://bugs.python.org/issue44518 opened by serhiy.storchaka #44521: str.removeprefix(): add strict: bool https://bugs.python.org/issue44521 opened by socketpair #44522: [doc] open() function errors='surrogateescape' has inaccurate https://bugs.python.org/issue44522 opened by bupjae2 #44524: __name__ attribute in typing module https://bugs.python.org/issue44524 opened by farcat #44525: Implement CALL_FUNCTION adaptive interpreter optimizations https://bugs.python.org/issue44525 opened by kj #44528: Move IP version resolving to http.server's API https://bugs.python.org/issue44528 opened by pavel-lexyr #44530: Propagate qualname from the compiler unit to code objects for https://bugs.python.org/issue44530 opened by Gabriele Tornetta #44531: Add _PyType_AllocNoTrack() function: allocate without tracking https://bugs.python.org/issue44531 opened by vstinner #44532: multi subinterpreters use _PyStructSequence_InitType failed. https://bugs.python.org/issue44532 opened by JunyiXie #44533: Where are the log file(s) https://bugs.python.org/issue44533 opened by tygrus #44534: unittest.mock.Mock.unsafe doc is garbled https://bugs.python.org/issue44534 opened by roysmith #44537: Document PGO in devguide https://bugs.python.org/issue44537 opened by gvanrossum #44539: Imghdr JPG Quantized https://bugs.python.org/issue44539 opened by mohamadmansourx #44540: venv: activate.bat fails for venv with special characters in P https://bugs.python.org/issue44540 opened by MB113 #44543: Remove depreciated logging.warn() method https://bugs.python.org/issue44543 opened by Harry-Lees #44544: Add full list of possible args to textwrap: wrap, fill, shorte https://bugs.python.org/issue44544 opened by andrei.avk #44547: fraction.Fraction does not implement __int__. https://bugs.python.org/issue44547 opened by mamrhein #44549: BZip 1.0.6 Critical Vulnerability https://bugs.python.org/issue44549 opened by s.s.mahato #44552: incomplete documentation of __main__.py https://bugs.python.org/issue44552 opened by mandolaerik #44553: types.Union should support GC https://bugs.python.org/issue44553 opened by kj Most recent 15 issues with no replies (15) == #44553: types.Union should support GC https://bugs.python.org/issue44553 #44552: incomplete documentation of __main__.py https://bugs.python.org/issue44552 #44549: BZip 1.0.6 Critical Vulnerability https://bugs.python.org/issue44549 #44540: venv: activate.bat fails for venv with special characters in P https://bugs.python.org/issue44540 #44539: Imghdr JPG Quantized https://bugs.python.org/issue44539 #44534: unittest.mock.Mock.unsafe doc is garbled https://bugs.python.org/issue44534 #44532: multi subinterpreters use _PyStructSequence_InitType failed. https://bugs.python.org/issue44532 #44528: Move IP version resolving to http.server's API https://bugs.python.org/issue44528 #44525: Implement CALL_FUNCTION adaptive interpreter optimizations https://bugs.python.org/issue44525 #44522: [doc] open() function errors='surrogateescape' has inaccurate https://bugs.python.org/issue44522 #44516: Update bundled pip to 21.1.3 https://bugs.python.org/issue44516 #44515: contextlib test incompatibility with non-refcounted GC https://bugs.python.org/issue44515 #44514: configparser.rst & bz2.rst leave temp files after 'make doctes https://bugs.python.org/issue44514 #44512: csv.DictWriter: inconsistency in handling of extrasaction arg https://bugs.python.org/issue44512 #44511: Improve the bytecode for mapping patterns https://bugs.python.org/issue44511 Most recent 15 issues waiting for
