There was a thread no long ago asking for help, As Gustavo and Jonathan said no one replied so it's better to not have one than to have a broken one.
The thing is that someone (even me) could sit down and make it happen but since I'm not a normal user of Elixir it will probably get outdated and broken in the next batch of commits to the quickstart, so unless we have a dedicated maintainer for TG2+elixir it's going to stay out of the trunk. That said it doesn't means that TG2 doesn't works with elixir, nor it means we don't encourage users to use it. We just don't want broken releases. That said given the way SA works you don't need auth.py to be elixir, so you could leave that as plain SA and make the rest of your code use Elixir On Tue, Jan 13, 2009 at 12:09 PM, Gustavo Narea <[email protected]> wrote: > > Hello, > > For Elixir to be supported, we need someone who knows Elixir and is willing to > support it. It seems like we have people who likes and knows Elixir, but > nobody who is willing to make TG2 support it. > > Want to jump in? ;-) > > Cheers. > > On Tuesday January 13, 2009 18:56:08 Helio Pereira wrote: >> Hi all, >> >> Why do you remove elixir from the turbogears 2? Elixir and SqlAlchemy >> must walk together in TG2 :-P >> >> PS: Elixir seems more understandable for newbies like me... >> >> Regards, >> Helio Pereira >> > -- > Gustavo Narea <http://gustavonarea.net/>. > > Get rid of unethical constraints! Get freedomware: > http://www.getgnulinux.org/ > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
