Rejeeve & Waylan:
Thanks for the pointers. I will check them out.
On May 7, 1:26 pm, "Waylan Limberg" <[EMAIL PROTECTED]> wrote:
> Another alternative is Django on IronPython. I'm not involved
> personally, but my understanding is that it currently works (at least
> to some extent) and there
First, maybe an apology is in order? I am sorry that if my post came
off harsh or chastising, my intent was to encourage.
"I think the comment is not harsh but very honest about the
current state of affairs, and this kind of candor is essential."
Agreed that candor is essential. How come the
Another alternative is Django on IronPython. I'm not involved
personally, but my understanding is that it currently works (at least
to some extent) and there is an effort underway to iron (sorry
couldn't resist) out the bugs. I could be wrong, but as IronPython is
basically python on .NET, I
On Wed, May 7, 2008 at 10:23 PM, rcs_comp <[EMAIL PROTECTED]> wrote:
> Just remember that there are people out there like me who see a lot of
> potential for Django but are confined to using IIS and MSSQL. Don't
> be skeptical of us, use our interest in Django to make the framework
> that
On Wed, May 7, 2008 at 11:53 AM, rcs_comp <[EMAIL PROTECTED]> wrote:
...
> Maybe I am reading too much into the comment, but I would like to
> encourage you to steer clear of the attitude behind this statement.
And I'd encourage you to quote in context-- a user had repeatedly
marked the ticket
I think it is perfectly reasonable to decide what platforms you are
interested in working with when you are contributing your efforts to
free software. Perhaps if you think Django should work better on IIS
you could work on it yourself or pay someone else to work on that,
rather than chastising
I came across this ticket:
http://code.djangoproject.com/ticket/2039
and was somewhat disappointed by one of the comments I read. I wrote
this response, but then realized it should probably come here rather
than go in the ticket system.
Replying to [comment:18
