On Sat, Apr 18, 2020 at 05:05:43PM +0200, Christoph Zwerschke wrote: > > Am 18.04.2020 um 16:19 schrieb Justin Pryzby: > > I don't think we came to any conclusion about this, and I cannot find > > it in github, and I cannot access trac... > > > > How should I use contants like ProgrammingError without incurring > > warnings from pylint ? Should I import _pg instead ? > > Can you check whether these pylint warnings disappear when you add an > "__all__" attribute to pg that contains "ProgrammingError" (and other public > globals)? I think we should do this anyway.
That didn't work. It did work to do this: ProgrammingError = _pg.ProgrammingError Maybe __all__ can *limits* what's visible but not extend it. ? -- Justin _______________________________________________ PyGreSQL mailing list PyGreSQL@Vex.Net https://mail.vex.net/mailman/listinfo/pygresql
