Am 20.02.2013 21:13, schrieb Bryan A. Jones:
> 1. The cycle of modify .spec / freeze / run / identify missing modules
> in .spec file can become tedious and, particularly for a new user,
> discouraging. This would Just Make It Work and provide helpful
> feedback on how to do so programmatically.

I totaly agree here. I'm jsut afarid, some logging would not help much.
>
> 2. The ImportError message may not be particularly revealing. From a
> recent post:
>

In this example such a logging would not help, simply because (as I
assume), there is no module imported. I assume in this example some
entry-pointe are searched. And if none is found the ImportError is
raised. This could not be catched by the solution you are proposing.

-- 
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP

Goebel Consult
http://www.goebel-consult.de

Monatliche Kolumne:
http://www.cissp-gefluester.de/2012-04-compliance-bringt-keine-sicherheit
Blog: http://www.goebel-consult.de/blog/20050707

Goebel Consult ist Mitglied bei http://www.7-it.de/

Attachment: smime.p7s
Description: S/MIME Kryptografische Unterschrift

Reply via email to