Nesting Custom Errors in Classes

DL Neil PythonList at DancesWithMice.info
Tue Jul 23 19:47:51 EDT 2019


On 24/07/19 10:07 AM, Cameron Simpson wrote:
> On 24Jul2019 07:21, DL Neil <PythonList at DancesWithMice.info> wrote:
...
> Get some linting tools. They're great for catching this kind of error.

SublimeText has SublimeLinter and PycodeStyle installed, but I'm still 
familiarising myself with ST. Nothing is reported.

Any advice/correction/improvement would be most welcome...


> The tricky bit with dynamic language like Python is that some naming 
> errors (missed imports) aren't apparent until the code passes through 
> that path. Linters can cover a lot of this with static analysis.

Exactly!
(PyTest and coverage tools were no help - they import correctly (and 
test adequately), but I didn't open those (separate) modules to notice 
the multiple import-s)

Hope springs eternal ... there must be a better way???

(well yes, not wishing to 'flog a dead horse' (nor any horse for that 
matter) I'm pleased at the (lack of negative) response to my allied 
question about nested classes, which would solve the original problem)

-- 
Regards =dn



More information about the Python-list mailing list