a/browse/CASSANDRA-875 — but rather than just
>> refactor the py_stress utility I'd like to make something that fulfils
>> whatever needs that the current utility fails to meet.
>>
>> I'm also curious about how you'd like me to commit/expose my code.
>> Originally I was thinking of creating a separate git repo, specific to this
>> utility, but have no issues working from a fork on Github either.
>>
>> Kind Regards,
>>
>> Kushal Pisavadia
>
>
--
Todd Lipcon
Software Engineer, Cloudera
that you can live
> with. Holding something like this to a vote is just going to invite flame
> wars and disagreements.
>
>
Can I vote +1 on this sentiment? :)
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
, Apr 13, 2010 at 1:09 PM, Pablo Cuadrado <
> >> pablocuadr...@gmail.com>wrote:
> >> >>>
> >> >>>> Well, so far we are:
> >> >>>>
> >> >>>> Pylons +3
> >> >>>> Tornado +2
> >> >>>> Django +1
> >> >>>> Undetermined +2
> >> >>>>
> >> >>>
> >> >>> +1 for pylons. I think a more popular framework is likely to have
> >> better
> >> >>> chances of being maintained and avoiding bitrot in the long haul.
> >> >>>
> >> >>> -Brandon
> >> >>>
> >> >
> >> >
> >>
> >
>
--
Todd Lipcon
Software Engineer, Cloudera
