home.social

#nogil — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nogil, aggregated by home.social.

  1. Проект Hornbeam — новый способ задеплоить ваше приложение на питоне

    Здравствуйте, дорогие читатели! Сегодня я расскажу вам о проекте hornbeam , который переводится на русский язык как "граб" - это такое дерево, похожее на дуб. Он позволяет деплоить сервисы на питоне, используя для этого виртуальную машину эрланга, BEAM (!) А также, позволяет удобно запускать код на питоне, если вы уже используете Erlang или Elixir. Фреймворк, на мой взгляд - полностью в духе эпохи, в которой доминируют питон, дата-саенс, машинное обучение и LLM, и в которой в программирование продолжают проникать полупрофессиональные инструменты из среды дата-саентистов и других энтузиастов - к счастью. Дошло уже до того, что инструменты и практики с почти безупречной репутацией, такие как kubernetes и контейнеризация, уступают место крайне любительскому подходу вроде "для инфраструктуры используйте эрланг". Проект задумал и осуществил автор широко известного веб-сервера gunicorn, он адресован широкому сообществу программистов на питоне и эрланге.

    habr.com/ru/articles/1009900/

    #python #erlang #nogil #ml #beam

  2. Проект Hornbeam — новый способ задеплоить ваше приложение на питоне

    Здравствуйте, дорогие читатели! Сегодня я расскажу вам о проекте hornbeam , который переводится на русский язык как "граб" - это такое дерево, похожее на дуб. Он позволяет деплоить сервисы на питоне, используя для этого виртуальную машину эрланга, BEAM (!) А также, позволяет удобно запускать код на питоне, если вы уже используете Erlang или Elixir. Фреймворк, на мой взгляд - полностью в духе эпохи, в которой доминируют питон, дата-саенс, машинное обучение и LLM, и в которой в программирование продолжают проникать полупрофессиональные инструменты из среды дата-саентистов и других энтузиастов - к счастью. Дошло уже до того, что инструменты и практики с почти безупречной репутацией, такие как kubernetes и контейнеризация, уступают место крайне любительскому подходу вроде "для инфраструктуры используйте эрланг". Проект задумал и осуществил автор широко известного веб-сервера gunicorn, он адресован широкому сообществу программистов на питоне и эрланге.

    habr.com/ru/articles/1009900/

    #python #erlang #nogil #ml #beam

  3. Проект Hornbeam — новый способ задеплоить ваше приложение на питоне

    Здравствуйте, дорогие читатели! Сегодня я расскажу вам о проекте hornbeam , который переводится на русский язык как "граб" - это такое дерево, похожее на дуб. Он позволяет деплоить сервисы на питоне, используя для этого виртуальную машину эрланга, BEAM (!) А также, позволяет удобно запускать код на питоне, если вы уже используете Erlang или Elixir. Фреймворк, на мой взгляд - полностью в духе эпохи, в которой доминируют питон, дата-саенс, машинное обучение и LLM, и в которой в программирование продолжают проникать полупрофессиональные инструменты из среды дата-саентистов и других энтузиастов - к счастью. Дошло уже до того, что инструменты и практики с почти безупречной репутацией, такие как kubernetes и контейнеризация, уступают место крайне любительскому подходу вроде "для инфраструктуры используйте эрланг". Проект задумал и осуществил автор широко известного веб-сервера gunicorn, он адресован широкому сообществу программистов на питоне и эрланге.

    habr.com/ru/articles/1009900/

    #python #erlang #nogil #ml #beam

  4. Has anyone benchmarked the Python with JIT vs non-JIT using 3.13 version?

    #python #JIT #nogil

  5. Has anyone benchmarked the Python with JIT vs non-JIT using 3.13 version?

    #python #JIT #nogil

  6. Has anyone benchmarked the Python with JIT vs non-JIT using 3.13 version?

    #python #JIT #nogil

  7. Has anyone benchmarked the Python with JIT vs non-JIT using 3.13 version?

    #python #JIT #nogil

  8. Has anyone benchmarked the Python with JIT vs non-JIT using 3.13 version?

    #python #JIT #nogil

  9. My weekend :python: project was building a new tool for Python projects, called “unittest-ft”, to run your entire test suite in parallel using a thread pool. With Python 3.13 and free threading enabled, this can dramatically speed up your test suite, as well as help catch any thread-safety issues that your project might have.

    It also includes options to run "stress tests" which queues every test to be run ten times rather than just once, as well as randomizing the test order every time to help catch unintended test order dependencies.

    This is intended for use with Python 3.13 or newer with free threading enabled, but is functionally useful back to Python 3.8 for testing and use in CI (it just won't be *faster* without FT).

    pypi.org/project/unittest-ft/

    #Python #FreeThreading #NoGIL

  10. My weekend :python: project was building a new tool for Python projects, called “unittest-ft”, to run your entire test suite in parallel using a thread pool. With Python 3.13 and free threading enabled, this can dramatically speed up your test suite, as well as help catch any thread-safety issues that your project might have.

    It also includes options to run "stress tests" which queues every test to be run ten times rather than just once, as well as randomizing the test order every time to help catch unintended test order dependencies.

    This is intended for use with Python 3.13 or newer with free threading enabled, but is functionally useful back to Python 3.8 for testing and use in CI (it just won't be *faster* without FT).

    pypi.org/project/unittest-ft/

    #Python #FreeThreading #NoGIL

  11. My weekend :python: project was building a new tool for Python projects, called “unittest-ft”, to run your entire test suite in parallel using a thread pool. With Python 3.13 and free threading enabled, this can dramatically speed up your test suite, as well as help catch any thread-safety issues that your project might have.

    It also includes options to run "stress tests" which queues every test to be run ten times rather than just once, as well as randomizing the test order every time to help catch unintended test order dependencies.

    This is intended for use with Python 3.13 or newer with free threading enabled, but is functionally useful back to Python 3.8 for testing and use in CI (it just won't be *faster* without FT).

    pypi.org/project/unittest-ft/

    #Python #FreeThreading #NoGIL

  12. My weekend :python: project was building a new tool for Python projects, called “unittest-ft”, to run your entire test suite in parallel using a thread pool. With Python 3.13 and free threading enabled, this can dramatically speed up your test suite, as well as help catch any thread-safety issues that your project might have.

    It also includes options to run "stress tests" which queues every test to be run ten times rather than just once, as well as randomizing the test order every time to help catch unintended test order dependencies.

    This is intended for use with Python 3.13 or newer with free threading enabled, but is functionally useful back to Python 3.8 for testing and use in CI (it just won't be *faster* without FT).

    pypi.org/project/unittest-ft/

    #Python #FreeThreading #NoGIL

  13. My weekend :python: project was building a new tool for Python projects, called “unittest-ft”, to run your entire test suite in parallel using a thread pool. With Python 3.13 and free threading enabled, this can dramatically speed up your test suite, as well as help catch any thread-safety issues that your project might have.

    It also includes options to run "stress tests" which queues every test to be run ten times rather than just once, as well as randomizing the test order every time to help catch unintended test order dependencies.

    This is intended for use with Python 3.13 or newer with free threading enabled, but is functionally useful back to Python 3.8 for testing and use in CI (it just won't be *faster* without FT).

    pypi.org/project/unittest-ft/

    #Python #FreeThreading #NoGIL

  14. I am FIRMLY team #python4 for the #nogil work. LFG. The lesson from Python 3 is you gotta rip off that upgrade bandaid. lwn.net/Articles/947138/

  15. I am FIRMLY team #python4 for the #nogil work. LFG. The lesson from Python 3 is you gotta rip off that upgrade bandaid. lwn.net/Articles/947138/

  16. I am FIRMLY team #python4 for the #nogil work. LFG. The lesson from Python 3 is you gotta rip off that upgrade bandaid. lwn.net/Articles/947138/

  17. I am FIRMLY team #python4 for the #nogil work. LFG. The lesson from Python 3 is you gotta rip off that upgrade bandaid. lwn.net/Articles/947138/

  18. I am FIRMLY team #python4 for the #nogil work. LFG. The lesson from Python 3 is you gotta rip off that upgrade bandaid. lwn.net/Articles/947138/

  19. I've been thinking about what #asyncio might look like in a #nogil #Python world, and I'm curious about what others are thinking too. So I made a Discourse discussion: discuss.python.org/t/asyncio-i

    Would love for folks to chip in with their thoughts!

  20. I've been thinking about what #asyncio might look like in a #nogil #Python world, and I'm curious about what others are thinking too. So I made a Discourse discussion: discuss.python.org/t/asyncio-i

    Would love for folks to chip in with their thoughts!

  21. I've been thinking about what #asyncio might look like in a #nogil #Python world, and I'm curious about what others are thinking too. So I made a Discourse discussion: discuss.python.org/t/asyncio-i

    Would love for folks to chip in with their thoughts!

  22. I've been thinking about what #asyncio might look like in a #nogil #Python world, and I'm curious about what others are thinking too. So I made a Discourse discussion: discuss.python.org/t/asyncio-i

    Would love for folks to chip in with their thoughts!

  23. I've been thinking about what #asyncio might look like in a #nogil #Python world, and I'm curious about what others are thinking too. So I made a Discourse discussion: discuss.python.org/t/asyncio-i

    Would love for folks to chip in with their thoughts!

  24. Big Python news! 🐍📰

    "Thank you, everyone, for responding to the poll on the no-GIL proposal. It’s clear that the overall sentiment is positive, both for the general idea and for PEP 703 specifically. The Steering Council is also largely positive on both. We intend to accept PEP 703, although we’re still working on the acceptance details."

    For the general plan, see:

    discuss.python.org/t/a-steerin #PEP703 #Python #GIL #NoGIL

  25. Big Python news! 🐍📰

    "Thank you, everyone, for responding to the poll on the no-GIL proposal. It’s clear that the overall sentiment is positive, both for the general idea and for PEP 703 specifically. The Steering Council is also largely positive on both. We intend to accept PEP 703, although we’re still working on the acceptance details."

    For the general plan, see:

    discuss.python.org/t/a-steerin #PEP703 #Python #GIL #NoGIL

  26. Big Python news! 🐍📰

    "Thank you, everyone, for responding to the poll on the no-GIL proposal. It’s clear that the overall sentiment is positive, both for the general idea and for PEP 703 specifically. The Steering Council is also largely positive on both. We intend to accept PEP 703, although we’re still working on the acceptance details."

    For the general plan, see:

    discuss.python.org/t/a-steerin #PEP703 #Python #GIL #NoGIL

  27. Big Python news! 🐍📰

    "Thank you, everyone, for responding to the poll on the no-GIL proposal. It’s clear that the overall sentiment is positive, both for the general idea and for PEP 703 specifically. The Steering Council is also largely positive on both. We intend to accept PEP 703, although we’re still working on the acceptance details."

    For the general plan, see:

    discuss.python.org/t/a-steerin #PEP703 #Python #GIL #NoGIL