That is the right place for issues with the backport; note that as a backport new features and issues that also exist in CPython's master/tip branch should be reported to the python bugtracker, where Paul pointed you.
Cheers, Rob On 22 August 2016 at 21:25, Cosimo Lupo <[email protected]> wrote: > Hello, > > Sorry if this is not the right place to ask this sorts of questions. > > The PyPI page for unittest2 package links to > https://code.google.com/archive/p/unittest-ext/issues as its "issue > tracker", however the Google Code pages seems to be read-only nowadays, so I > can't open new issues there. > > I've found an auto-exported Github clone for unittest-ext and opened a new > issue there: https://github.com/testing-cabal/unittest-ext/issues/99 > > However I'm not sure it's the right one, as there doesn't seem to be much > activity in there. > > It would be good to know where I should report bugs for unittest2. > Thank you! > > -- > > Cosimo Lupo > > > _______________________________________________ > Distutils-SIG maillist - [email protected] > https://mail.python.org/mailman/listinfo/distutils-sig > _______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
