First, the obvious alternative: Rails.
I would argue that many of the advantages RoR had are starting to go away.
The two obvious advantages were Heroku and schema migration. Heroku now
supports Python and Django... done. While Django has had South, the problem
is that not everyone used it. This s
On 2014-08-10 01:06, Josh Johnson wrote:
> Django documentation is phenomenal,
I second Josh's comment. I'd naively assumed that all "big Python
web-framework" documentation was as good as Django's. However, when I
had to do some work on a contract involving CherryPy and
SQLObject...marcy was it
On Sunday, August 10, 2014 2:37:01 AM UTC-7, Aymeric Augustin wrote:
Using GitHub for auth a giant +1 from me.
For me, this ranks up with the SVN to Github move as a: "Why hasn't this
been done already?"
Daniel Greenfeld
co-author Two Scoops of Django
--
You received this message because
Am 09.08.2014 21:21, schrieb Aymeric Augustin:
I tried to support both Trac auth and GitHub auth but I couldn't make it work.
The argument that "I use GitHub but maybe someone else doesn't want to" came up
a few times in this discussion. It seems to me that it's a theoretical concern about an
Django documentation is phenomenal, leagues better than ROR's - the ability
to dial back and look at documentation for legacy version of django and
filter out the newer features is also amazing.
I decided to go the python/django route based solely on the ease of finding
exactly what I needed in
Don't worry, I remapped permissions to GitHub usernames. Curtis, I lowercased
your username, you should still have admin rights.
There were a few usernames I had never seen and couldn't identify. If you think
you lost permissions, please get in touch privately.
As said earlier by Florian, it's
