Add config argument to more password.Password invocations. The work done to allow password_pbkdf2_default_rounds to be overridden for testing requires that calls to password.Password include a config argument. This was needed because using the real value more than quadrupled testing runtime. However there are still a few places where config was not being set when Password was called. I think this fixes all of the ones that are called from a function that have access to a db.config object. The remaining ones all call Password(encrypted=x). This results in Password.unpack() being called. If x is not a propertly formatted password string ("{scheme}...", it calls encodePassword. It then should end up raising the ConfigNotSet exception. This is probably what we want as it means the shape of "x" is not correct. I don't understand why Password.unpack() attempts to encrypt the value of encrypted if it doesn't match the right form. According to codecov, this encryption branch is being used, so somewhere x is of the wrong form. Hmmm....

.. meta::
    :description:
        Table of contents for published documentation on the Roundup
        Issue Tracker.

Docs
====

.. toctree::
   :maxdepth: 2

   docs/features
   docs/installation
   docs/upgrading
   docs/security
   docs/FAQ
   docs/user_guide
   docs/customizing
   docs/admin_guide
   docs/debugging
   docs/xmlrpc
   docs/rest
   docs/tracker_templates
   docs/glossary
   docs/acknowledgements
   docs/license
   Design Overview <docs/overview>
   Design (original) <docs/design>
   docs/developers
   Notes about the MySQL Database backend <docs/mysql>
   Notes about the PostgreSQL Database backend <docs/postgresql>
   Richard Jones implementation notes <docs/implementation>