encukou/test-2 — Issue #38: Port to Pyramid
Author: encukou
Created: 2011-11-03 19:39:21+00:00
State: open
Labels: assigned-to Eevee, fixed-in 2011 Q1, high-priority, involved, plugin core, refactor

**Reported by [Eevee](http://bugs.veekun.com/users/1) on 2010/11/07 21:48:00 +0000 · Migrated from [Redmine issue 440](http://bugs.veekun.com/issues/440)**

---

Pylons is as good as dead. See: [http://docs.pylonshq.com](http://docs.pylonshq.com)/

It looks like its replacement, Pyramid, is a much better fit for spline’s plugin shenanigans anyway. Maybe this could be a good start towards making spline a real project.

Definitely don’t merge this until Pyramid has a non-alpha release.

Redmine metadata:
Updated on: 2011/04/28 21:27:50 +0000
Start date: 2010/11/07
Relations:
duplicated #608

---

**Comment by [Eevee](http://bugs.veekun.com/users/1) from 2011/04/22 04:43:24 +0000**

Might be nice to bail on setuptools at the same time. Not sure what Pyramid relies on, if it relies on anything.

---

**Comment by [Eevee](http://bugs.veekun.com/users/1) from 2011/04/28 21:27:50 +0000**

Things about Pylons that bother me that I would like to move away from in the process, if Pyramid isn’t bolted tightly to them:

- Setuptools.
- Nose.
- Paster in general, its absurd config file, etc.

Things about spline that are broken and this is a good chance to fix them since I’ll wreck everything in the process anyway:

- Where plugin resources live. We have JS, CSS, generic static files, templates, model code, and controllers. Each are namespaced independently. Makes for kind of a mess. Seems like plugins should act as self-contained as possible, but still be able to interact with each other if they ask nicely.
- How the “local” plugin works. At the moment it’s an isolated Python file, which is frightening.

category_id: None ⇨ 37