Re: Bug Reports
- From:
- Zed A. Shaw
- Date:
- 2009-11-12 @ 08:27
On Thu, Nov 12, 2009 at 12:22:45AM -0700, Chad Woolley wrote:
> Is there a ticket system? No occurrence of 'bug' on the "about" page.
> Anyway, here they are...
Thanks man, I'll look at these.
> Dunno what you wrote Fretwar in (no 'source' or 'code' occurence on
> about page either), but there's a certain web framework written in
> Ruby which has conventions to prevent problems like #5 ;)
Yes, but if I wrote it in Rails, then I would have had to follow the
convention of the week, updates, testing flavor of the month, changes to
shoulda or rspec or whatever, assholes, people who think rails is all
there is, and would never have done a full concept site like this with
scalable hosting in less than a month in my spare time on weekends.
Instead, I'd still be trying to figure out why my routing seems to load
up arbitrary ruby files, or why Matz changed all of Enumerable, or why
Array seems to leak ram.
--
Zed A. Shaw
http://zedshaw.com/
Re: Bug Reports
- From:
- Zed A. Shaw
- Date:
- 2009-11-12 @ 09:05
On Thu, Nov 12, 2009 at 12:27:34AM -0800, Zed A. Shaw wrote:
> > Dunno what you wrote Fretwar in (no 'source' or 'code' occurence on
> > about page either), but there's a certain web framework written in
> > Ruby which has conventions to prevent problems like #5 ;)
The fix in web.py is:
return render.player_edit(who, failure="Passwords do not match.")
becomes:
return render.player_edit(i, failure="Passwords do not match.")
who is the database object for the player, i is the form input. They're
interchangeable in web.py so it's just a simple coding mistake.
--
Zed A. Shaw
http://zedshaw.com/