2009/11/23 Michal Kwiatkowski <email address hidden>:
> Pythoscope failed because of an exception, that is a bug and I'll fix
> that.
>
> Another issue is whether Pythoscope should inspect modules that it
> ignored earlier but were explicitly specified on the command line. I
> would say yes, it should do that. In your particular case pythoscope
> should notice that ".my_cool_class.py" wasn't inspected earlier, so it
> should inspect it and then generate tests for it. Do you think that's a
> good solution?
Yes, or if Pythoscope can't inspect an entity for some reason, it
should not try to generate a test and log that fact.
It would also be nice if the initial inspection would log the fact
that it is ignoring things.
Note that although my testcase is a valid python script, it is not a
valid module: it can not be imported due to restrictions on Python
names.
2009/11/23 Michal Kwiatkowski <email address hidden>:
> Pythoscope failed because of an exception, that is a bug and I'll fix
> that.
>
> Another issue is whether Pythoscope should inspect modules that it
> ignored earlier but were explicitly specified on the command line. I
> would say yes, it should do that. In your particular case pythoscope
> should notice that ".my_cool_class.py" wasn't inspected earlier, so it
> should inspect it and then generate tests for it. Do you think that's a
> good solution?
Yes, or if Pythoscope can't inspect an entity for some reason, it
should not try to generate a test and log that fact.
It would also be nice if the initial inspection would log the fact
that it is ignoring things.
Note that although my testcase is a valid python script, it is not a
valid module: it can not be imported due to restrictions on Python
names.