Ahet is looking for a maintainer

45 views
Skip to first unread message

Mike Orr

unread,
Sep 18, 2011, 10:19:49 PM9/18/11
to pylons-...@googlegroups.com
Would anyone like to take over maintenance of Akhet? I'm not inclined
to update it anymore except for essential bugfixes, but maybe somebody
would like to add updates for Pyramid 1.2 and the debug toolbar and
take Akhet beyond what it is. My interest at this point is more in
documentation and perhaps adding a little bit to the Akhet library,
than in adding to the application skeleton. You could move it to
Github if you wish, or leave it at Bitbucket.

--
Mike Orr <slugg...@gmail.com>

Ergo

unread,
Sep 21, 2011, 9:04:29 AM9/21/11
to pylons-...@googlegroups.com
I was suggested that I could maintain it, so be it ;-)

I can take over - we would move it to github - to have everything under pylons project.

Ergo

unread,
Sep 21, 2011, 9:07:49 AM9/21/11
to pylons-...@googlegroups.com
One thing i was planning to do would be implementing this recipie:

https://docs.pylonsproject.org/projects/pyramid_cookbook/dev/sqla.html#using-a-non-global-session and have Akhet use the non-global database session.

Chris McDonough

unread,
Sep 21, 2011, 2:22:28 PM9/21/11
to pylons-...@googlegroups.com

Sounds good to me... let's do it via IRC.

- C


>
>
> --
> You received this message because you are subscribed to the Google
> Groups "pylons-discuss" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/pylons-discuss/-/slLygKle4q8J.
> To post to this group, send email to pylons-...@googlegroups.com.
> To unsubscribe from this group, send email to pylons-discuss
> +unsub...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/pylons-discuss?hl=en.


Mike Orr

unread,
Sep 21, 2011, 4:57:00 PM9/21/11
to pylons-...@googlegroups.com
OK Ergo, go for it.

That looks fine.

The second half of that article I'm not so hot about, a configuration
that depends on config.scan(). Akhet has avoided that so far.

So would you use SQLAHelper at all then? It basically acts as a shared
container for the dbsession, engines, and declarative base. Perhaps
for simplicity you could drop it for the default configuration, and
just mention in the documentation or comments that it's useful for
multi-db or multi-module models.

--
Mike Orr <slugg...@gmail.com>

Chris Withers

unread,
Sep 23, 2011, 1:10:30 PM9/23/11
to pylons-...@googlegroups.com, Ergo

I wrote a package basically for managing SQLALchemy sessions in Pyramid
applications:

http://packages.python.org/mortar_rdb/use.html

Ignore the schema versioning stuff if you want, it's not a necessary
part of the equation...

any problems, shout my way...

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

Reply all
Reply to author
Forward
0 new messages