home.social

Search

491 results for “nedbat”

  1. @coveragepy can now use Python 3.12's new sys.monitoring module with much lower overhead.

    On 3.12, it's about the same as if you were running tests *without* coverage enabled!

    nedbatchelder.com/blog/202312/

    With 7.4.2, you can set COVERAGE_CORE=sysmon globally on your CI, and it'll only use it where available (Python 3.12 and 3.13 alpha), and use the default for 3.11 and older.

    For example, @pillow is 9% - 27% faster!

    github.com/python-pillow/Pillo

    #Python #coverage #CoveragePy #pytest #testing #CI

  2. @coveragepy can now use Python 3.12's new sys.monitoring module with much lower overhead.

    On 3.12, it's about the same as if you were running tests *without* coverage enabled!

    nedbatchelder.com/blog/202312/

    With 7.4.2, you can set COVERAGE_CORE=sysmon globally on your CI, and it'll only use it where available (Python 3.12 and 3.13 alpha), and use the default for 3.11 and older.

    For example, @pillow is 9% - 27% faster!

    github.com/python-pillow/Pillo

    #Python #coverage #CoveragePy #pytest #testing #CI

  3. @coveragepy can now use Python 3.12's new sys.monitoring module with much lower overhead.

    On 3.12, it's about the same as if you were running tests *without* coverage enabled!

    nedbatchelder.com/blog/202312/

    With 7.4.2, you can set COVERAGE_CORE=sysmon globally on your CI, and it'll only use it where available (Python 3.12 and 3.13 alpha), and use the default for 3.11 and older.

    For example, @pillow is 9% - 27% faster!

    github.com/python-pillow/Pillo

    #Python #coverage #CoveragePy #pytest #testing #CI

  4. @coveragepy can now use Python 3.12's new sys.monitoring module with much lower overhead.

    On 3.12, it's about the same as if you were running tests *without* coverage enabled!

    nedbatchelder.com/blog/202312/

    With 7.4.2, you can set COVERAGE_CORE=sysmon globally on your CI, and it'll only use it where available (Python 3.12 and 3.13 alpha), and use the default for 3.11 and older.

    For example, @pillow is 9% - 27% faster!

    github.com/python-pillow/Pillo

    #Python #coverage #CoveragePy #pytest #testing #CI

  5. Helpful article in setting up a badge without using 3rd-party . I was able to adapt the instructions using instead of tox as outlined in the link. Good stuff, Maynard.

    nedbatchelder.com/blog/202209/

  6. @benfulton @leahawasser I think most Python tools that measure cyclomatic complexity are based on or use McCabe, from @nedbat (pypi.org/project/mccabe/). has it built-in, has plugins (McCabe is one), probably has it built-in too.

  7. Ned Batchelder is officially kicking off PyCon US 2023 presentations with his keynote in the Grand Ballroom of the Salt Lake City Convention Center 🗣️🐍🇺🇲

    CC @pycon @PyConUS @nedbat

  8. @ob A good option is to maintain a literate source file, then process using Cog to get the dotfile.

    nedbatchelder.com/code/cog/ind

  9. One of the things I enjoy the most at conferences like PyCon US is exactly this atmosphere around the hallway track.

    So many spontaneous conversations, shared experiences, community stories, and people genuinely interested in collaborating and helping each other 🙂

    CC @grandstaff @sheena @pamelafox @nedbat

  10. Oh look, it's another riveting novel on the #thrilling #escapades of #mocking in Python! 🎉 In this episode, our hero discovers that if you incorrectly place a mock, it can *gasp* break later! 😱 Spoiler: it's as exciting as watching paint dry, only with more #JSON. 🐢💥
    nedbatchelder.com/blog/202511/ #Python #programming #software #development #HackerNews #ngated

  11. 🎩 Ah, the age-old debate: #Testing vs. #DSA - because who needs efficient algorithms when you can just test your way to success? 🤡 Apparently, knowing whether your code works is more important than knowing how it works. 🔍 But hey, at least you won't be asked to write unit tests during interviews... right? 🙃
    nedbatchelder.com/blog/202509/ #softwaredevelopment #codinginterviews #programminghumor #HackerNews #ngated

  12. Practically, I find it very helpful to write the change log item as an update to the change log document, included *as separately written documentation*, one change among others included in the same merge request.

    Consider it like updating the API documentation in the same merge request that changes the API. Except here, the interface is for the humans considering whether and why to update to this version.

    And a tool like towncrier.readthedocs.io/ can help a lot.

    @xavdid @nedbat

  13. Practically, I find it very helpful to write the change log item as an update to the change log document, included *as separately written documentation*, one change among others included in the same merge request.

    Consider it like updating the API documentation in the same merge request that changes the API. Except here, the interface is for the humans considering whether and why to update to this version.

    And a tool like #TownCrier towncrier.readthedocs.io/ can help a lot.

    @xavdid @nedbat

  14. Practically, I find it very helpful to write the change log item as an update to the change log document, included *as separately written documentation*, one change among others included in the same merge request.

    Consider it like updating the API documentation in the same merge request that changes the API. Except here, the interface is for the humans considering whether and why to update to this version.

    And a tool like #TownCrier towncrier.readthedocs.io/ can help a lot.

    @xavdid @nedbat

  15. Practically, I find it very helpful to write the change log item as an update to the change log document, included *as separately written documentation*, one change among others included in the same merge request.

    Consider it like updating the API documentation in the same merge request that changes the API. Except here, the interface is for the humans considering whether and why to update to this version.

    And a tool like #TownCrier towncrier.readthedocs.io/ can help a lot.

    @xavdid @nedbat

  16. Practically, I find it very helpful to write the change log item for a merge request as an update to the change log document, included *as separately written documentation* in the merge request itself.

    Consider it like updating the API documentation in the same merge request that changes the API. Except here, the interface is for the humans considering whether and why to update to this version.

    And a tool like #TownCrier towncrier.readthedocs.io/ can help a lot.

    @xavdid @nedbat

  17. Сбор покрытия Flask (Python) в Runtime

    Всем привет, меня зовут Осипов Станислав. Я занимаюсь AppSec/DevOps с 2021 года. В этой статье я хочу рассказать как можно собрать покрытие Python приложения в runtime (незавершая процесс). Что было использовано для сбора покрытия: github.com/pallets/flask - Flask 3.03 github.com/nedbat/coveragepy - coverage 7.5.1

    habr.com/ru/articles/812861/

    #покрытие_кода #flask #coveragepy #runtime

  18. Сбор покрытия Flask (Python) в Runtime

    Всем привет, меня зовут Осипов Станислав. Я занимаюсь AppSec/DevOps с 2021 года. В этой статье я хочу рассказать как можно собрать покрытие Python приложения в runtime (незавершая процесс). Что было использовано для сбора покрытия: github.com/pallets/flask - Flask 3.03 github.com/nedbat/coveragepy - coverage 7.5.1

    habr.com/ru/articles/812861/

    #покрытие_кода #flask #coveragepy #runtime

  19. Сбор покрытия Flask (Python) в Runtime

    Всем привет, меня зовут Осипов Станислав. Я занимаюсь AppSec/DevOps с 2021 года. В этой статье я хочу рассказать как можно собрать покрытие Python приложения в runtime (незавершая процесс). Что было использовано для сбора покрытия: github.com/pallets/flask - Flask 3.03 github.com/nedbat/coveragepy - coverage 7.5.1

    habr.com/ru/articles/812861/

    #покрытие_кода #flask #coveragepy #runtime

  20. Сбор покрытия Flask (Python) в Runtime

    Всем привет, меня зовут Осипов Станислав. Я занимаюсь AppSec/DevOps с 2021 года. В этой статье я хочу рассказать как можно собрать покрытие Python приложения в runtime (незавершая процесс). Что было использовано для сбора покрытия: github.com/pallets/flask - Flask 3.03 github.com/nedbat/coveragepy - coverage 7.5.1

    habr.com/ru/articles/812861/

    #покрытие_кода #flask #coveragepy #runtime

  21. »Twitter is one web site, run by one corporation. This is easy to understand, and makes it easy to find lots of people, but has the disadvantage that a deranged over-leveraged misanthropic moron can buy it and make it terrible.«

    nedbatchelder.com/blog/202211/

    #mastodon #server #twitter #deranged #overveveraged #misanthropic #moron

  22. RE: mastodon.online/@universalhub/

    For anyone at that heard me explain this Boston Python mascot:

  23. I'm getting emails from Michael Foord's email address asking me to update my voidspace.org.uk links to voidspace.uk. They are not answering my questions. The site does seem to have moved. Anyone have any information about this?

  24. Pervasive alt text is great, it helps include everyone. As it happens, I don't need the alt text. Is there a way in to not display it when I click into an image? Often the overlay obscures part of the image so I have to click the alt to expand it then dismiss it to see everythin.

  25. Pervasive alt text is great, it helps include everyone. As it happens, I don't need the alt text. Is there a way in #Phanpy to not display it when I click into an image? Often the overlay obscures part of the image so I have to click the alt to expand it then dismiss it to see everythin.

  26. Can you really claim to support recent Python versions if you don't have 3.16 in your CI matrix?
    github.com/coveragepy/coverage

  27. RE: mastodon.social/@AlSweigart/11

    It's hard to express how great Pablo's keynote was. One for the ages (to over-extend his metaphor).

  28. As usual, Adam Silkey brings a rousing and important lightning talk: "We can build a better world"

  29. Juggling open space today at 3:45 (start of the afternoon break) in the hall outside room 103.

    Join us, we will teach you! No one has ever regretted it!!

  30. Loving the support and love for Brazilian speaker Vinícius Gubiani Ferreira: us.pycon.org/2026/schedule/pre