Paster, Pylons, and iPython

[Michael Pedersen]

So, I did some research on this ticket:  https://sourceforge.net/p/turbogears2/tickets/110/

As it turns out, we have compatibility issues, and our first real issue that's due to Pylons basically stopping. What do you all want to see happen? I've listed the options in this comment: https://sourceforge.net/p/turbogears2/tickets/110/?limit=10&page=0#2798

Thoughts, everyone?

--
Michael J. Pedersen
My IM IDs: Jabber/pede...@icelus.tzo.com, AIM/pedermj022171
          Yahoo/pedermj2002, MSN/pederm...@hotmail.com
My Online Resume: http://www.icelus.org/
Twitter: pedersentg

[Diez B. Roggisch]

On Sep 30, 2011, at 4:27 AM, Michael Pedersen wrote:

So, I did some research on this ticket:  https://sourceforge.net/p/turbogears2/tickets/110/

As it turns out, we have compatibility issues, and our first real issue that's due to Pylons basically stopping. What do you all want to see happen? I've listed the options in this comment: https://sourceforge.net/p/turbogears2/tickets/110/?limit=10&page=0#2798

Thoughts, everyone?

I tried to inform myself about the current state of pylons 1.0 - and I'm a bit confused: the website tells us, it's in "maintenance mode". Which IMHO would mean that a pull-request for such a fix as the above should be accepted, and eventually lead to a new release.

But if that's not going to happen, and given that TG2 relies heavily on Pylons - is there really an option other than stepping up ourselves & maintain Pylons? Or replace it, of course. Which would deem me as somewhat daunting.

Diez

[Alessandro Molina]

I would start by asking to Ben Bangert if there is any consideration
about releasing a bugfix version of Pylons.
Maybe they are not against doing it but they don't have many reasons to do it.

About TG approach, to such issues, as far as I have seen in the past
the solution has been to monkeypatch Pylons.

Anyway there are places where TG doesn't practically rely on pylons
(like template rendering) so I would suggest to start removing pylons
dependency from those places so that we can minimize the impact of
pylons issues.

> --
> You received this message because you are subscribed to the Google Groups
> "TurboGears" group.
> To post to this group, send email to turbo...@googlegroups.com.
> To unsubscribe from this group, send email to
> turbogears+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/turbogears?hl=en.
>

[Andronikos]

It works with iPython 0.10.2, so it may not be such a big deal after all.

A.

[julien tayon]

pyramid is supposed to be the continuation of pylons. Does migration
implies a lot of refactoring ?

Plus pyramid have these gorgeous iron maiden like' T shirts.

http://laflamme.storenvy.com/products/66831-pyramid-not-built-by-aliens-t-shirt

[Michael Pedersen]

For now, I've asked Ben Bangert if he can do a maintenance release, and explained we have an open ticket we have to address. Hopefully, I'll hear from him soon, and with a positive response.

We're definitely not ready for taking over Pylons ourselves, nor are we ready to switch to Pyramid. There's enough differences between Pylons and Pyramid that, without a compability layer, we'd have a lot of work ahead for us.

--
You received this message because you are subscribed to the Google Groups "TurboGears" group.

To post to this group, send email to turbo...@googlegroups.com.
To unsubscribe from this group, send email to turbogears+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.