Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #72453

Re: Strange Behavior

References <CANYcpZy3qZHRORFPTnvPcSV+uU2MHHPPcKuDXXuRvjNJBnKJKg@mail.gmail.com> <mailman.10571.1401732331.18130.python-list@python.org> <538d1532$0$29978$c3e8da3$5496439d@news.astraweb.com> <CAPTjJmp6Kiyk66-=s7bfig-mfRCd-8ij+ZFp7cbuOA+3cFEw-Q@mail.gmail.com>
Date 2014-06-02 17:49 -0700
Subject Re: Strange Behavior
From Igor Korot <ikorot01@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.10581.1401756954.18130.python-list@python.org> (permalink)

Show all headers | View raw


On Mon, Jun 2, 2014 at 5:30 PM, Chris Angelico <rosuav@gmail.com> wrote:
> On Tue, Jun 3, 2014 at 10:22 AM, Steven D'Aprano
> <steve+comp.lang.python@pearwood.info> wrote:
>> On Mon, 02 Jun 2014 20:05:29 +0200, robertw89 wrote:
>>
>>> I invoked the wrong bug.py :/ , works fine now (this happens to me when
>>> im a bit tired sometimes...).
>>
>> Clarity in naming is an excellent thing. If you have two files called
>> "bug.py", that's two too many.
>>
>> Imagine having fifty files called "program.py". Which one is which? How
>> do you know? Programs should be named by what they do (think of Word,
>> which does word processing, or Photoshop, which does photo editing), or
>> when that isn't practical, at least give them a unique and memorable name
>> (Outlook, Excel). The same applies to files demonstrating bugs.
>
> Heh. I agree, but I've been guilty of this exact problem myself.
> Suppose you have a program that segfaults when given certain input, so
> you take the input that crashes it, and progressively simplify it
> until you have a minimal test-case. What do you call the file that
> you're editing? What if you have a few different variants? I've had a
> few called "boom" and "boom2" and "booooooom" and so on, because
> there's really nothing else to call it - if I knew what the cause of
> the crash was, I wouldn't be naming the testcase files, I'd be fixing
> the problem.


test1, test2, test3, .... testn.
At least it will be unique. ;-)

Thank you.

>
> ChrisA
> --
> https://mail.python.org/mailman/listinfo/python-list

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Strange Behavior robertw89@googlemail.com - 2014-06-02 20:05 +0200
  Re: Strange Behavior Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-06-03 00:22 +0000
    Re: Strange Behavior Chris Angelico <rosuav@gmail.com> - 2014-06-03 10:30 +1000
    Re: Strange Behavior Igor Korot <ikorot01@gmail.com> - 2014-06-02 17:49 -0700
    Choosing good names for things is difficult (was: Strange Behavior) Ben Finney <ben@benfinney.id.au> - 2014-06-03 10:57 +1000
      Re: Choosing good names for things is difficult (was: Strange Behavior) Rustom Mody <rustompmody@gmail.com> - 2014-06-02 19:06 -0700
        Re: Choosing good names for things is difficult (was: Strange Behavior) Chris Angelico <rosuav@gmail.com> - 2014-06-03 13:33 +1000
    Re: Strange Behavior Peter Otten <__peter__@web.de> - 2014-06-03 10:01 +0200
      Re: Strange Behavior Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-06-03 11:44 +0000

csiph-web