Pretty impressive it is still working. Is the codebase still using Python
2?
The last page of the document that Mike linked seems like the best starting
point:
https://docs.pylonsproject.org/projects/pyramid_cookbook/en/latest/pylons/migrate.html
I guess it also depends on how many resources you
I've been using Formencode throughout for both form validation and
config settings validation. Thanks for porting it to Pyramid and
Python 3 and dealing with changes within Python 3: I remember all of
those broke functionality until Formencode was patched.
On Tue, Apr 1, 2025 at 2:20 PM Jonathan V
Pyramid offers a few ways to implement the routes/controllers.
The easiest when porting from Pylons is to use classes with @viewconfig,
that can mimic the pylons handler classes.
This is a good example of that approach in the regular pyramid
docs:
https://docs.pylonsproject.org/projects/pyrami
Maybe a little off-topic, but the first idea springing to my mind when I
read about converting Genshi templates into something else is "Why not go
all the way to front-end development?"
Of course, it would be more work than just migrating to a classic Pyramid
app (although the Python part would be
Here's the information the Pylons developers and core users at the
time used to migrate their applications to Pyramid.
https://docs.pylonsproject.org/projects/pyramid_cookbook/en/latest/pylons/index.html
(Pyramid Cookbook, section "Pyramid for Pylons Users", written by me)
That was in 2012. I migra
Hello,
We are planning to migrate an existing project from Pylons 1.0.2 to Pyramid
2.x.
What would be the best approach to start?
I understand we need to rewrite all the controllers.
We are using Genshi templates and this does not seem to be supported in
Pyramid 2. What would be the easiest temp
