#zope — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #zope, aggregated by home.social.
-
@jensens had a very interesting series of talks yesterday at the World Plone Day about his recent experiments:
- A PostgreSQL JSONB ZODB storage backend
- PostgreSQL based Plone catalog
- S3 storage for blobs
- Thumbor for image scaling
- Tika for content extraction from office documentshttps://www.youtube.com/watch?v=K8YOjRaGSNQ&list=PLGN9BI-OAQkRXyVRChYlsJNIsOahQqUhd&index=12
-
@jensens had a very interesting series of talks yesterday at the World Plone Day about his recent experiments:
- A PostgreSQL JSONB ZODB storage backend
- PostgreSQL based Plone catalog
- S3 storage for blobs
- Thumbor for image scaling
- Tika for content extraction from office documentshttps://www.youtube.com/watch?v=K8YOjRaGSNQ&list=PLGN9BI-OAQkRXyVRChYlsJNIsOahQqUhd&index=12
-
@jensens had a very interesting series of talks yesterday at the World Plone Day about his recent experiments:
- A PostgreSQL JSONB ZODB storage backend
- PostgreSQL based Plone catalog
- S3 storage for blobs
- Thumbor for image scaling
- Tika for content extraction from office documentshttps://www.youtube.com/watch?v=K8YOjRaGSNQ&list=PLGN9BI-OAQkRXyVRChYlsJNIsOahQqUhd&index=12
-
@jensens had a very interesting series of talks yesterday at the World Plone Day about his recent experiments:
- A PostgreSQL JSONB ZODB storage backend
- PostgreSQL based Plone catalog
- S3 storage for blobs
- Thumbor for image scaling
- Tika for content extraction from office documentshttps://www.youtube.com/watch?v=K8YOjRaGSNQ&list=PLGN9BI-OAQkRXyVRChYlsJNIsOahQqUhd&index=12
-
@jensens had a very interesting series of talks yesterday at the World Plone Day about his recent experiments:
- A PostgreSQL JSONB ZODB storage backend
- PostgreSQL based Plone catalog
- S3 storage for blobs
- Thumbor for image scaling
- Tika for content extraction from office documentshttps://www.youtube.com/watch?v=K8YOjRaGSNQ&list=PLGN9BI-OAQkRXyVRChYlsJNIsOahQqUhd&index=12
-
ZODB has served the Zope and Plone community for over two decades. But its storage model — opaque pickle blobs and BTree-based catalog indexes — hasn't aged well. You can't query your data with SQL. You can't inspect object state without unpickling. And the catalog is a black box that lives inside the very database it indexes.
Time to change that. Four modules, one mission — get ZODB out of the pickle jar.
https://community.plone.org/t/zodb-out-of-the-pickle-jar/22832
-
ZODB has served the Zope and Plone community for over two decades. But its storage model — opaque pickle blobs and BTree-based catalog indexes — hasn't aged well. You can't query your data with SQL. You can't inspect object state without unpickling. And the catalog is a black box that lives inside the very database it indexes.
Time to change that. Four modules, one mission — get ZODB out of the pickle jar.
https://community.plone.org/t/zodb-out-of-the-pickle-jar/22832
-
ZODB has served the Zope and Plone community for over two decades. But its storage model — opaque pickle blobs and BTree-based catalog indexes — hasn't aged well. You can't query your data with SQL. You can't inspect object state without unpickling. And the catalog is a black box that lives inside the very database it indexes.
Time to change that. Four modules, one mission — get ZODB out of the pickle jar.
https://community.plone.org/t/zodb-out-of-the-pickle-jar/22832
-
ZODB has served the Zope and Plone community for over two decades. But its storage model — opaque pickle blobs and BTree-based catalog indexes — hasn't aged well. You can't query your data with SQL. You can't inspect object state without unpickling. And the catalog is a black box that lives inside the very database it indexes.
Time to change that. Four modules, one mission — get ZODB out of the pickle jar.
https://community.plone.org/t/zodb-out-of-the-pickle-jar/22832
-
ZODB has served the Zope and Plone community for over two decades. But its storage model — opaque pickle blobs and BTree-based catalog indexes — hasn't aged well. You can't query your data with SQL. You can't inspect object state without unpickling. And the catalog is a black box that lives inside the very database it indexes.
Time to change that. Four modules, one mission — get ZODB out of the pickle jar.
https://community.plone.org/t/zodb-out-of-the-pickle-jar/22832
-
It was a fun combo-conference in Finland recently! PloneConf and PyCon Finland 👏
Released by CultRepo in August 2025, watch the documentary for free on YouTube 🎬 https://www.youtube.com/watch?v=GfH4QL4VqJ0
#opensource #python #guidovanrossum #zope #historyofplone #historyofpython #historyofzope #pauleveritt #jimfulton #digitalcreations #zoteroplone
-
It was a fun combo-conference in Finland recently! PloneConf and PyCon Finland 👏
Released by CultRepo in August 2025, watch the documentary for free on YouTube 🎬 https://www.youtube.com/watch?v=GfH4QL4VqJ0
#opensource #python #guidovanrossum #zope #historyofplone #historyofpython #historyofzope #pauleveritt #jimfulton #digitalcreations #zoteroplone
-
It was a fun combo-conference in Finland recently! PloneConf and PyCon Finland 👏
Released by CultRepo in August 2025, watch the documentary for free on YouTube 🎬 https://www.youtube.com/watch?v=GfH4QL4VqJ0
#opensource #python #guidovanrossum #zope #historyofplone #historyofpython #historyofzope #pauleveritt #jimfulton #digitalcreations #zoteroplone
-
It was a fun combo-conference in Finland recently! PloneConf and PyCon Finland 👏
Released by CultRepo in August 2025, watch the documentary for free on YouTube 🎬 https://www.youtube.com/watch?v=GfH4QL4VqJ0
#opensource #python #guidovanrossum #zope #historyofplone #historyofpython #historyofzope #pauleveritt #jimfulton #digitalcreations #zoteroplone
-
It was a fun combo-conference in Finland recently! PloneConf and PyCon Finland 👏
Released by CultRepo in August 2025, watch the documentary for free on YouTube 🎬 https://www.youtube.com/watch?v=GfH4QL4VqJ0
#opensource #python #guidovanrossum #zope #historyofplone #historyofpython #historyofzope #pauleveritt #jimfulton #digitalcreations #zoteroplone
-
Nil Bacardit & Roger Boixader Güell demo Guillotina Volto: A New Backend for Volto
https://2025.ploneconf.org/schedule/talks/guillotina-volto-a-new-backend-for-volto
#PloneConf2025 #Plone #Python #Volto #ReactJS #OpenSource #CMS #Zope #Pyramid #Django #RestAPI
-
Nil Bacardit & Roger Boixader Güell demo Guillotina Volto: A New Backend for Volto
https://2025.ploneconf.org/schedule/talks/guillotina-volto-a-new-backend-for-volto
#PloneConf2025 #Plone #Python #Volto #ReactJS #OpenSource #CMS #Zope #Pyramid #Django #RestAPI
-
Nil Bacardit & Roger Boixader Güell demo Guillotina Volto: A New Backend for Volto
https://2025.ploneconf.org/schedule/talks/guillotina-volto-a-new-backend-for-volto
#PloneConf2025 #Plone #Python #Volto #ReactJS #OpenSource #CMS #Zope #Pyramid #Django #RestAPI
-
Nil Bacardit & Roger Boixader Güell demo Guillotina Volto: A New Backend for Volto
https://2025.ploneconf.org/schedule/talks/guillotina-volto-a-new-backend-for-volto
#PloneConf2025 #Plone #Python #Volto #ReactJS #OpenSource #CMS #Zope #Pyramid #Django #RestAPI
-
Nil Bacardit & Roger Boixader Güell demo Guillotina Volto: A New Backend for Volto
https://2025.ploneconf.org/schedule/talks/guillotina-volto-a-new-backend-for-volto
#PloneConf2025 #Plone #Python #Volto #ReactJS #OpenSource #CMS #Zope #Pyramid #Django #RestAPI
-
Andreas Jung presents Experiences with AI in Software Projects
https://2025.ploneconf.org/schedule/talks/experiences-with-ai-in-software-projects
#PloneConf2025 #Plone #Python #Volto #ReactJS #Zope #OpenSource #AI #ArtificialIntelligence #VibeCoding #FastAPI
-
Andreas Jung presents Experiences with AI in Software Projects
https://2025.ploneconf.org/schedule/talks/experiences-with-ai-in-software-projects
#PloneConf2025 #Plone #Python #Volto #ReactJS #Zope #OpenSource #AI #ArtificialIntelligence #VibeCoding #FastAPI
-
Andreas Jung presents Experiences with AI in Software Projects
https://2025.ploneconf.org/schedule/talks/experiences-with-ai-in-software-projects
#PloneConf2025 #Plone #Python #Volto #ReactJS #Zope #OpenSource #AI #ArtificialIntelligence #VibeCoding #FastAPI
-
Andreas Jung presents Experiences with AI in Software Projects
https://2025.ploneconf.org/schedule/talks/experiences-with-ai-in-software-projects
#PloneConf2025 #Plone #Python #Volto #ReactJS #Zope #OpenSource #AI #ArtificialIntelligence #VibeCoding #FastAPI
-
Andreas Jung presents Experiences with AI in Software Projects
https://2025.ploneconf.org/schedule/talks/experiences-with-ai-in-software-projects
#PloneConf2025 #Plone #Python #Volto #ReactJS #Zope #OpenSource #AI #ArtificialIntelligence #VibeCoding #FastAPI
-
Guido Stevens of https://quaive.com presents Living Software for a Living World
https://2025.ploneconf.org/schedule/talks/living-software-for-a-living-world
#PloneConf2025 #Plone #Python #Volto #ReactJS #Zope #OpenSource #CaseStudy
-
Guido Stevens of https://quaive.com presents Living Software for a Living World
https://2025.ploneconf.org/schedule/talks/living-software-for-a-living-world
#PloneConf2025 #Plone #Python #Volto #ReactJS #Zope #OpenSource #CaseStudy
-
Guido Stevens of https://quaive.com presents Living Software for a Living World
https://2025.ploneconf.org/schedule/talks/living-software-for-a-living-world
#PloneConf2025 #Plone #Python #Volto #ReactJS #Zope #OpenSource #CaseStudy
-
Guido Stevens of https://quaive.com presents Living Software for a Living World
https://2025.ploneconf.org/schedule/talks/living-software-for-a-living-world
#PloneConf2025 #Plone #Python #Volto #ReactJS #Zope #OpenSource #CaseStudy
-
Guido Stevens of https://quaive.com presents Living Software for a Living World
https://2025.ploneconf.org/schedule/talks/living-software-for-a-living-world
#PloneConf2025 #Plone #Python #Volto #ReactJS #Zope #OpenSource #CaseStudy
-
Vienna poetry school - first Perl based CMS in 1997, Zope ZClasses in 2001, I'm maintaining it since 2002, Plone 4 in 2010. Relaunch planning started in 2018 and after some attempts and different approaches, after 16 years of its Plone 4 Relaunch and more than 30 since sfd was founded I relaunched it today using Plone 6.1, ClassicUI, fully ajaxified.
I'm happy. -
Vienna poetry school - first Perl based CMS in 1997, Zope ZClasses in 2001, I'm maintaining it since 2002, Plone 4 in 2010. Relaunch planning started in 2018 and after some attempts and different approaches, after 16 years of its Plone 4 Relaunch and more than 30 since sfd was founded I relaunched it today using Plone 6.1, ClassicUI, fully ajaxified.
I'm happy. -
Vienna poetry school - first Perl based CMS in 1997, Zope ZClasses in 2001, I'm maintaining it since 2002, Plone 4 in 2010. Relaunch planning started in 2018 and after some attempts and different approaches, after 16 years of its Plone 4 Relaunch and more than 30 since sfd was founded I relaunched it today using Plone 6.1, ClassicUI, fully ajaxified.
I'm happy. -
Vienna poetry school - first Perl based CMS in 1997, Zope ZClasses in 2001, I'm maintaining it since 2002, Plone 4 in 2010. Relaunch planning started in 2018 and after some attempts and different approaches, after 16 years of its Plone 4 Relaunch and more than 30 since sfd was founded I relaunched it today using Plone 6.1, ClassicUI, fully ajaxified.
I'm happy. -
Vienna poetry school - first Perl based CMS in 1997, Zope ZClasses in 2001, I'm maintaining it since 2002, Plone 4 in 2010. Relaunch planning started in 2018 and after some attempts and different approaches, after 16 years of its Plone 4 Relaunch and more than 30 since sfd was founded I relaunched it today using Plone 6.1, ClassicUI, fully ajaxified.
I'm happy. -
#Zope wydało nowe wersje paczek, usuwając przestrzenie nazw typu pkg-resources.
Całkowicie normalny sposób aktualizacji paczek w #Gentoo:
1. Na początek, zachowaj oryginalne obejście na testy (tworzenie własnego `__init__.py`).
2. Zauważ, że kolejna paczka się sypie, bo testy oczekują ścieżek względem podkatalogu `zope`. Pomiń ją na razie.
3. Przy następnej paczce uświadom sobie, że zamiast powyższego obejścia możesz po prostu wejść do podkatalogu `zope`. Wróć się i zaktualizuj poprzednie paczki, włącznie z tą, która się sypała.
4. Z powrotem do aktualizacji. Przy następnej paczce zauważ, że już wcześniej miałeś lepsze rozwiązanie: zamiast `cd` było `python -m unittest -s …`. No więc z powrotem, i znów wszystkie paczki na to jedno rozwiązania.
5. No i dalsze paczki. Przy kolejnej okazuje się, że ta jednak oczekuje ścieżek względem głównego katalogu site-packages… No dobra, zrobimy hybrydę `__init__.py` z `python -m unitest -s …`. -
#Zope wydało nowe wersje paczek, usuwając przestrzenie nazw typu pkg-resources.
Całkowicie normalny sposób aktualizacji paczek w #Gentoo:
1. Na początek, zachowaj oryginalne obejście na testy (tworzenie własnego `__init__.py`).
2. Zauważ, że kolejna paczka się sypie, bo testy oczekują ścieżek względem podkatalogu `zope`. Pomiń ją na razie.
3. Przy następnej paczce uświadom sobie, że zamiast powyższego obejścia możesz po prostu wejść do podkatalogu `zope`. Wróć się i zaktualizuj poprzednie paczki, włącznie z tą, która się sypała.
4. Z powrotem do aktualizacji. Przy następnej paczce zauważ, że już wcześniej miałeś lepsze rozwiązanie: zamiast `cd` było `python -m unittest -s …`. No więc z powrotem, i znów wszystkie paczki na to jedno rozwiązania.
5. No i dalsze paczki. Przy kolejnej okazuje się, że ta jednak oczekuje ścieżek względem głównego katalogu site-packages… No dobra, zrobimy hybrydę `__init__.py` z `python -m unitest -s …`. -
#Zope wydało nowe wersje paczek, usuwając przestrzenie nazw typu pkg-resources.
Całkowicie normalny sposób aktualizacji paczek w #Gentoo:
1. Na początek, zachowaj oryginalne obejście na testy (tworzenie własnego `__init__.py`).
2. Zauważ, że kolejna paczka się sypie, bo testy oczekują ścieżek względem podkatalogu `zope`. Pomiń ją na razie.
3. Przy następnej paczce uświadom sobie, że zamiast powyższego obejścia możesz po prostu wejść do podkatalogu `zope`. Wróć się i zaktualizuj poprzednie paczki, włącznie z tą, która się sypała.
4. Z powrotem do aktualizacji. Przy następnej paczce zauważ, że już wcześniej miałeś lepsze rozwiązanie: zamiast `cd` było `python -m unittest -s …`. No więc z powrotem, i znów wszystkie paczki na to jedno rozwiązania.
5. No i dalsze paczki. Przy kolejnej okazuje się, że ta jednak oczekuje ścieżek względem głównego katalogu site-packages… No dobra, zrobimy hybrydę `__init__.py` z `python -m unitest -s …`. -
#Zope wydało nowe wersje paczek, usuwając przestrzenie nazw typu pkg-resources.
Całkowicie normalny sposób aktualizacji paczek w #Gentoo:
1. Na początek, zachowaj oryginalne obejście na testy (tworzenie własnego `__init__.py`).
2. Zauważ, że kolejna paczka się sypie, bo testy oczekują ścieżek względem podkatalogu `zope`. Pomiń ją na razie.
3. Przy następnej paczce uświadom sobie, że zamiast powyższego obejścia możesz po prostu wejść do podkatalogu `zope`. Wróć się i zaktualizuj poprzednie paczki, włącznie z tą, która się sypała.
4. Z powrotem do aktualizacji. Przy następnej paczce zauważ, że już wcześniej miałeś lepsze rozwiązanie: zamiast `cd` było `python -m unittest -s …`. No więc z powrotem, i znów wszystkie paczki na to jedno rozwiązania.
5. No i dalsze paczki. Przy kolejnej okazuje się, że ta jednak oczekuje ścieżek względem głównego katalogu site-packages… No dobra, zrobimy hybrydę `__init__.py` z `python -m unitest -s …`. -
So #Zope released new versions of their packages, with pkg-resources style namespace removal.
Totally normal way to do the bumps:
1. At first, keep the existing testing hack (writing `__init__.py`).
2. Notice that the next package fails because it expects test paths relative to `zope` subdirectory. Skip it for now.
3. While doing the next package, realize you could remove that hack and simply run tests within the `zope` subdirectory! Go back and update all the previous packages, including the one that failed before.
4. Back to bumping. Notice that in the very next package you've had an even better solution: instead of `cd`, you just called `python -m unittest -s …`. Go back and update all the previous packages.
5. Back to bumping. The very next package turns out to actually expects test paths relative to the top-level site-packages directory. Well, you can use a hybrid of the `__init__.py` hack with `python -m unittest -s …`. -
So #Zope released new versions of their packages, with pkg-resources style namespace removal.
Totally normal way to do the bumps:
1. At first, keep the existing testing hack (writing `__init__.py`).
2. Notice that the next package fails because it expects test paths relative to `zope` subdirectory. Skip it for now.
3. While doing the next package, realize you could remove that hack and simply run tests within the `zope` subdirectory! Go back and update all the previous packages, including the one that failed before.
4. Back to bumping. Notice that in the very next package you've had an even better solution: instead of `cd`, you just called `python -m unittest -s …`. Go back and update all the previous packages.
5. Back to bumping. The very next package turns out to actually expects test paths relative to the top-level site-packages directory. Well, you can use a hybrid of the `__init__.py` hack with `python -m unittest -s …`. -
So #Zope released new versions of their packages, with pkg-resources style namespace removal.
Totally normal way to do the bumps:
1. At first, keep the existing testing hack (writing `__init__.py`).
2. Notice that the next package fails because it expects test paths relative to `zope` subdirectory. Skip it for now.
3. While doing the next package, realize you could remove that hack and simply run tests within the `zope` subdirectory! Go back and update all the previous packages, including the one that failed before.
4. Back to bumping. Notice that in the very next package you've had an even better solution: instead of `cd`, you just called `python -m unittest -s …`. Go back and update all the previous packages.
5. Back to bumping. The very next package turns out to actually expects test paths relative to the top-level site-packages directory. Well, you can use a hybrid of the `__init__.py` hack with `python -m unittest -s …`. -
So #Zope released new versions of their packages, with pkg-resources style namespace removal.
Totally normal way to do the bumps:
1. At first, keep the existing testing hack (writing `__init__.py`).
2. Notice that the next package fails because it expects test paths relative to `zope` subdirectory. Skip it for now.
3. While doing the next package, realize you could remove that hack and simply run tests within the `zope` subdirectory! Go back and update all the previous packages, including the one that failed before.
4. Back to bumping. Notice that in the very next package you've had an even better solution: instead of `cd`, you just called `python -m unittest -s …`. Go back and update all the previous packages.
5. Back to bumping. The very next package turns out to actually expects test paths relative to the top-level site-packages directory. Well, you can use a hybrid of the `__init__.py` hack with `python -m unittest -s …`. -
So #Zope released new versions of their packages, with pkg-resources style namespace removal.
Totally normal way to do the bumps:
1. At first, keep the existing testing hack (writing `__init__.py`).
2. Notice that the next package fails because it expects test paths relative to `zope` subdirectory. Skip it for now.
3. While doing the next package, realize you could remove that hack and simply run tests within the `zope` subdirectory! Go back and update all the previous packages, including the one that failed before.
4. Back to bumping. Notice that in the very next package you've had an even better solution: instead of `cd`, you just called `python -m unittest -s …`. Go back and update all the previous packages.
5. Back to bumping. The very next package turns out to actually expects test paths relative to the top-level site-packages directory. Well, you can use a hybrid of the `__init__.py` hack with `python -m unittest -s …`. -
TIL about special comments in chameleon:
https://chameleon.readthedocs.io/en/latest/reference.html#markup-comments
-
TIL about special comments in chameleon:
https://chameleon.readthedocs.io/en/latest/reference.html#markup-comments
-
TIL about special comments in chameleon:
https://chameleon.readthedocs.io/en/latest/reference.html#markup-comments
-
PyCon Finland is back after almost a decade! As part of the annual Plone Conference, welcome to Jyväskylä on October 17, 2025! 🐍 Call for proposals is now open and early bird tickets available https://pyconfi.ploneconf.org/
#Plone #ploneconf2025 #Python #PyConFi #PyCon #React #Webdevelopment #opensource #universityofjyvaskyla #zope
-
PyCon Finland is back after almost a decade! As part of the annual Plone Conference, welcome to Jyväskylä on October 17, 2025! 🐍 Call for proposals is now open and early bird tickets available https://pyconfi.ploneconf.org/
#Plone #ploneconf2025 #Python #PyConFi #PyCon #React #Webdevelopment #opensource #universityofjyvaskyla #zope
-
PyCon Finland is back after almost a decade! As part of the annual Plone Conference, welcome to Jyväskylä on October 17, 2025! 🐍 Call for proposals is now open and early bird tickets available https://pyconfi.ploneconf.org/
#Plone #ploneconf2025 #Python #PyConFi #PyCon #React #Webdevelopment #opensource #universityofjyvaskyla #zope
-
PyCon Finland is back after almost a decade! As part of the annual Plone Conference, welcome to Jyväskylä on October 17, 2025! 🐍 Call for proposals is now open and early bird tickets available https://pyconfi.ploneconf.org/
#Plone #ploneconf2025 #Python #PyConFi #PyCon #React #Webdevelopment #opensource #universityofjyvaskyla #zope
-
PyCon Finland is back after almost a decade! As part of the annual Plone Conference, welcome to Jyväskylä on October 17, 2025! 🐍 Call for proposals is now open and early bird tickets available https://pyconfi.ploneconf.org/
#Plone #ploneconf2025 #Python #PyConFi #PyCon #React #Webdevelopment #opensource #universityofjyvaskyla #zope
-
Jens Klein @jensens of https://kleinundpartner.at explains mxmake - an opinionated way to use make for development and deployment on Python projects (and Zope/Plone) #plone #plone6 #wpd2025 #CMS #Python #React #volto #opensource #community #mxmake #zope https://youtu.be/ocSZI4iF8cc
-
Jens Klein @jensens of https://kleinundpartner.at explains mxmake - an opinionated way to use make for development and deployment on Python projects (and Zope/Plone) #plone #plone6 #wpd2025 #CMS #Python #React #volto #opensource #community #mxmake #zope https://youtu.be/ocSZI4iF8cc
-
Jens Klein @jensens of https://kleinundpartner.at explains mxmake - an opinionated way to use make for development and deployment on Python projects (and Zope/Plone) #plone #plone6 #wpd2025 #CMS #Python #React #volto #opensource #community #mxmake #zope https://youtu.be/ocSZI4iF8cc
-
Jens Klein @jensens of https://kleinundpartner.at explains mxmake - an opinionated way to use make for development and deployment on Python projects (and Zope/Plone) #plone #plone6 #wpd2025 #CMS #Python #React #volto #opensource #community #mxmake #zope https://youtu.be/ocSZI4iF8cc
-
Jens Klein @jensens of https://kleinundpartner.at explains mxmake - an opinionated way to use make for development and deployment on Python projects (and Zope/Plone) #plone #plone6 #wpd2025 #CMS #Python #React #volto #opensource #community #mxmake #zope https://youtu.be/ocSZI4iF8cc
-
Luciano De Fazio - Gestão de Processos Eletrônicos em Python / Zope https://2024.ploneconf.org/en/schedule/talks/gestao-de-processos-eletronicos-em-python-zope #ploneconf2024 #pythoncerrado2024 #brasilia #opensource #python #zope
-
Luciano De Fazio - Gestão de Processos Eletrônicos em Python / Zope https://2024.ploneconf.org/en/schedule/talks/gestao-de-processos-eletronicos-em-python-zope #ploneconf2024 #pythoncerrado2024 #brasilia #opensource #python #zope
-
Luciano De Fazio - Gestão de Processos Eletrônicos em Python / Zope https://2024.ploneconf.org/en/schedule/talks/gestao-de-processos-eletronicos-em-python-zope #ploneconf2024 #pythoncerrado2024 #brasilia #opensource #python #zope