pytest-postgresql 6.1.1__tar.gz → 7.0.1__tar.gz

{pytest_postgresql-6.1.1 → pytest_postgresql-7.0.1}/AUTHORS.rst

@@ -17,4 +17,4 @@ of pytest-postgresql along its history.
 * Donald Stufft
 * Will Vaughn
 * Hugo (hugovk)
-* Damian Skrzypczak
+* Damian Skrzypczak

{pytest_postgresql-6.1.1 → pytest_postgresql-7.0.1}/CHANGES.rst

@@ -3,13 +3,82 @@ CHANGELOG
 
 .. towncrier release notes start
 
+7.0.1 (2025-03-19)
+==================
+
+Bugfixes
+--------
+
+- Close postgresql connection after loading sql files.
+
+  Fixes possible `ResourceWarning`
+- Fixed an issue, where defining load paths in ini/toml configuration would fail
+  due to pytest's LocalPath not having an endswith method.
+
+
+7.0.0 (2025-02-23)
+==================
+
+Breaking changes
+----------------
+
+- Drop support for load parameter from client fixtures. This can be easily replaced by creating intermediary fixture between test and client fixture. (`#1087 <https://github.com/dbfixtures/pytest-postgresql/issues/1087>`__)
+- Stop supporting Python 3.8 as it already reached EOL
+
+
+Bugfixes
+--------
+
+- Passing all environment variables to the initdb.
+
+  This helps the cases where og_ctl is replaced by custom shell script
+  making additional calls, and needs all the variables, that ie server process gets. (`#1076 <https://github.com/dbfixtures/pytest-postgresql/issues/1076>`__)
+
+
+Features
+--------
+
+- If a test run ended in an error that prevented proper test cleanup,
+  developer can now use `--postgresql-drop-test-database` command line flag,
+  to delete database from noproc fixture at the start. (`#265 <https://github.com/dbfixtures/pytest-postgresql/issues/265>`__)
+- DatabaseJanitor.cursor now accepts optional parameter dbname, which defaults to `postgres`
+
+  This database name is used to make connection to and return a cursor. (`#265 <https://github.com/dbfixtures/pytest-postgresql/issues/265>`__)
+- When running tests with xdist, pytest-postgresql now attempts to detect random ports
+  selected by other nodes by writing down a .port file in session temporary directory.
+
+  The number of tries it attempts to select unused port is configurable,
+  and defaults to 0.
+
+  In case pytest-postgresql won't be able to select unused port,
+  PortForException is thrown with appropriate message. (`#872 <https://github.com/dbfixtures/pytest-postgresql/issues/872>`__)
+- Mark Python 3.13 as supported.
+
+
+Miscellaneus
+------------
+
+- `#707 <https://github.com/dbfixtures/pytest-postgresql/issues/707>`__, `#895 <https://github.com/dbfixtures/pytest-postgresql/issues/895>`__, `#1047 <https://github.com/dbfixtures/pytest-postgresql/issues/1047>`__, `#1048 <https://github.com/dbfixtures/pytest-postgresql/issues/1048>`__, `#1055 <https://github.com/dbfixtures/pytest-postgresql/issues/1055>`__, `#1061 <https://github.com/dbfixtures/pytest-postgresql/issues/1061>`__, `#1062 <https://github.com/dbfixtures/pytest-postgresql/issues/1062>`__, `#1063 <https://github.com/dbfixtures/pytest-postgresql/issues/1063>`__, `#1081 <https://github.com/dbfixtures/pytest-postgresql/issues/1081>`__
+- Add PostgreSQL 17 to CI and drop 12
+- Add [bot] suffix to the pre-commit actor.
+- Adjust links after repository transfer
+- Adjust workflows for actions-reuse 3.0.1
+- Fix DatabaseJanitor documentation.
+- In Python 3.13, usage of a positional argument for `maxsplit` has been
+  formally deprecated.
+  Update code to use keyword argument `maxsplit` instead of positional.
+- Skip local hooks from ci
+- Skip newsfragment checks for pre-commit actor.
+- Update pre-commit configuration to use ruff instead of flake8/pydocstyle
+
+
 6.1.1 (2024-09-05)
 ==================
 
 Bugfixes
 --------
 
-- Set minimum version of `port-for` dependecy in pyproject.toml for client installations. (`#1015 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/1015>`__)
+- Set minimum version of `port-for` dependecy in pyproject.toml for client installations. (`#1015 <https://github.com/dbfixtures/pytest-postgresql/issues/1015>`__)
 
 
 6.1.0 (2024-09-04)
@@ -18,13 +87,13 @@ Bugfixes
 Features
 --------
 
-- add support for \\ character in pytest temporary path (`#982 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/982>`__)
+- add support for \\ character in pytest temporary path (`#982 <https://github.com/dbfixtures/pytest-postgresql/issues/982>`__)
 
 
 Miscellaneus
 ------------
 
-- Add test for `PR #965 <https://github.com/ClearcodeHQ/pytest-postgresql/pull/965>`_
+- Add test for `PR #965 <https://github.com/dbfixtures/pytest-postgresql/pull/965>`_
 - refactors test_executor.py to enable Mac
 
 
@@ -35,13 +104,13 @@ Bugfixes
 --------
 
 - Fixed a long-standing bug, where calls to pg_ctl weren't getting `LC_*` and `LANG` envvars,
-  which caused issues on some systems not recognizing --auth parameter. (`#343 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/343>`__)
+  which caused issues on some systems not recognizing --auth parameter. (`#343 <https://github.com/dbfixtures/pytest-postgresql/issues/343>`__)
 
 
 Miscellaneus
 ------------
 
-- `#945 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/945>`__
+- `#945 <https://github.com/dbfixtures/pytest-postgresql/issues/945>`__
 
 
 6.0.0 (2024-03-11)
@@ -50,13 +119,13 @@ Miscellaneus
 Breaking changes
 ----------------
 
-- DatabaseJanitor class now accepts only keyword arguments. (`#899 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/899>`__)
+- DatabaseJanitor class now accepts only keyword arguments. (`#899 <https://github.com/dbfixtures/pytest-postgresql/issues/899>`__)
 
 
 Bugfixes
 --------
 
-- Fix the remaining `DepcrecationWarning` for `datetime.datetime.utcnow` on Python 3.12. (`#896 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/896>`__)
+- Fix the remaining `DepcrecationWarning` for `datetime.datetime.utcnow` on Python 3.12. (`#896 <https://github.com/dbfixtures/pytest-postgresql/issues/896>`__)
 
 
 Deprecations
@@ -65,7 +134,7 @@ Deprecations
 - Deprecated load parameter on a client fixture.
   Developers are encouraged to either use the load function/parameter
   for process fixture, or create an intermediate fixture placed between client
-  and tests themselves to fill in the data. (`#850 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/850>`__)
+  and tests themselves to fill in the data. (`#850 <https://github.com/dbfixtures/pytest-postgresql/issues/850>`__)
 
 
 Features
@@ -73,18 +142,18 @@ Features
 
 - Now all sql files used to initialise database for tests, has to be passed as pathlib.Path instance.
 
-  This helps the DatabaseJanitor choose correct behaviour based on parameter. (`#638 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/638>`__)
+  This helps the DatabaseJanitor choose correct behaviour based on parameter. (`#638 <https://github.com/dbfixtures/pytest-postgresql/issues/638>`__)
 - Have separate parameters for template database name and database name in DatabaseJanitor.
-  It'll make it much clearer to understand the code and Janitor's behaviour. (`#672 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/672>`__)
+  It'll make it much clearer to understand the code and Janitor's behaviour. (`#672 <https://github.com/dbfixtures/pytest-postgresql/issues/672>`__)
 - Template databases are now created with is_template flag turned on, and not by setting allow_connections to false.
 
-  The allow_connections flag being set to false is used strictly right before we attempt to drop the database. (`#914 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/914>`__)
+  The allow_connections flag being set to false is used strictly right before we attempt to drop the database. (`#914 <https://github.com/dbfixtures/pytest-postgresql/issues/914>`__)
 
 
 Miscellaneus
 ------------
 
-- `#865 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/865>`__, `#882 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/882>`__, `#893 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/893>`__, `#900 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/900>`__
+- `#865 <https://github.com/dbfixtures/pytest-postgresql/issues/865>`__, `#882 <https://github.com/dbfixtures/pytest-postgresql/issues/882>`__, `#893 <https://github.com/dbfixtures/pytest-postgresql/issues/893>`__, `#900 <https://github.com/dbfixtures/pytest-postgresql/issues/900>`__
 
 
 5.1.1 (2024-03-07)
@@ -93,7 +162,7 @@ Miscellaneus
 Miscellaneus
 ------------
 
-- Add missing python 3.12 classifier to pythin package. (`#915 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/915>`__)
+- Add missing python 3.12 classifier to pythin package. (`#915 <https://github.com/dbfixtures/pytest-postgresql/issues/915>`__)
 
 
 5.1.0 (2024-01-29)
@@ -102,26 +171,26 @@ Miscellaneus
 Bugfixes
 --------
 
-- Update postgresql_load default value for it to fallback into the empty list (`#881 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/881>`__)
+- Update postgresql_load default value for it to fallback into the empty list (`#881 <https://github.com/dbfixtures/pytest-postgresql/issues/881>`__)
 
 
 Features
 --------
 
-- Support for Python 3.12 (`#835 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/835>`__)
+- Support for Python 3.12 (`#835 <https://github.com/dbfixtures/pytest-postgresql/issues/835>`__)
 
 
 Miscellaneus
 ------------
 
-- Removed misleading parapgraph from one example in a README (`#688 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/688>`__)
-- Fixed typing exceptions for mypy 1.4 (`#765 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/765>`__)
-- README: fix section markup (`#771 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/771>`__, `#776 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/776>`__)
-- Add SQLAlchemy example for initialising common database state. (`#797 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/797>`__)
+- Removed misleading parapgraph from one example in a README (`#688 <https://github.com/dbfixtures/pytest-postgresql/issues/688>`__)
+- Fixed typing exceptions for mypy 1.4 (`#765 <https://github.com/dbfixtures/pytest-postgresql/issues/765>`__)
+- README: fix section markup (`#771 <https://github.com/dbfixtures/pytest-postgresql/issues/771>`__, `#776 <https://github.com/dbfixtures/pytest-postgresql/issues/776>`__)
+- Add SQLAlchemy example for initialising common database state. (`#797 <https://github.com/dbfixtures/pytest-postgresql/issues/797>`__)
 - Rely on cached/artifacted Pipfile.lock.
-  That way, it will be specifically defined for given python version/system. (`#834 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/834>`__)
-- CI Change - Add PostgreSQL 16, drop PostgreSQL 11 (`#836 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/836>`__)
-- Replace usage of `pkg_resources.parse_version` with `packaging.version.parse` (`#858 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/858>`__)
+  That way, it will be specifically defined for given python version/system. (`#834 <https://github.com/dbfixtures/pytest-postgresql/issues/834>`__)
+- CI Change - Add PostgreSQL 16, drop PostgreSQL 11 (`#836 <https://github.com/dbfixtures/pytest-postgresql/issues/836>`__)
+- Replace usage of `pkg_resources.parse_version` with `packaging.version.parse` (`#858 <https://github.com/dbfixtures/pytest-postgresql/issues/858>`__)
 
 
 5.0.0 (2023-05-20)
@@ -130,7 +199,7 @@ Miscellaneus
 Breaking changes
 ----------------
 
-- Drop support for Python 3.7 (`#706 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/706>`__)
+- Drop support for Python 3.7 (`#706 <https://github.com/dbfixtures/pytest-postgresql/issues/706>`__)
 - psycopg is now a mandatory requirement.
   With pyscop2 it was optional due to the different ways it could be installed:
 
@@ -138,32 +207,32 @@ Breaking changes
   * psycopg2-binary - binary distribution
   * psycopg2cffi - pypy enabled version
 
-  Since psycopg version 3 there's only one package to install. (`#744 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/744>`__)
-- Dropped --postgresql-logsprefix/postgresql_logsprefix options. All fixture data is already distinguished by tmpdir itself. (`#748 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/748>`__)
+  Since psycopg version 3 there's only one package to install. (`#744 <https://github.com/dbfixtures/pytest-postgresql/issues/744>`__)
+- Dropped --postgresql-logsprefix/postgresql_logsprefix options. All fixture data is already distinguished by tmpdir itself. (`#748 <https://github.com/dbfixtures/pytest-postgresql/issues/748>`__)
 
 
 Features
 --------
 
-- Re-rise FileNotFound errors with more meaningful messages. (`#598 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/598>`__)
-- Support Python 3.11 (`#678 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/678>`__)
+- Re-rise FileNotFound errors with more meaningful messages. (`#598 <https://github.com/dbfixtures/pytest-postgresql/issues/598>`__)
+- Support Python 3.11 (`#678 <https://github.com/dbfixtures/pytest-postgresql/issues/678>`__)
 
 
 Miscellaneus
 ------------
 
-- Drop PyPy from CI (`#669 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/669>`__)
-- pytest-postgresql will now recognise and use development postgresql versions (`#691 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/691>`__)
-- Use towncrier to maintain project's newsfragments/changelog (`#700 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/700>`__)
-- Move project dependency management to pipenv (`#701 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/701>`__)
-- Migrate to shared automerge workflow for automatic tests dependency updates (`#702 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/702>`__)
-- Use tbump instead of bumpversion to manage versioning and releases. (`#703 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/703>`__)
-- Move most of package configuration to pyproject.toml (`#704 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/704>`__)
-- Introduce Typed config dict (`#706 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/706>`__)
-- Use ankane/setup-postgres@v1 to setup postgresql in CI instead of custom scripts. (`#708 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/708>`__)
-- Pass codecov_token to codecov action to upload coverage. (`#721 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/721>`__)
-- Replaced flake8 and pydocstyle with ruff, turned on isort rules (`#735 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/735>`__)
-- Split single bid test job into smaller running each after another. (`#740 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/740>`__)
+- Drop PyPy from CI (`#669 <https://github.com/dbfixtures/pytest-postgresql/issues/669>`__)
+- pytest-postgresql will now recognise and use development postgresql versions (`#691 <https://github.com/dbfixtures/pytest-postgresql/issues/691>`__)
+- Use towncrier to maintain project's newsfragments/changelog (`#700 <https://github.com/dbfixtures/pytest-postgresql/issues/700>`__)
+- Move project dependency management to pipenv (`#701 <https://github.com/dbfixtures/pytest-postgresql/issues/701>`__)
+- Migrate to shared automerge workflow for automatic tests dependency updates (`#702 <https://github.com/dbfixtures/pytest-postgresql/issues/702>`__)
+- Use tbump instead of bumpversion to manage versioning and releases. (`#703 <https://github.com/dbfixtures/pytest-postgresql/issues/703>`__)
+- Move most of package configuration to pyproject.toml (`#704 <https://github.com/dbfixtures/pytest-postgresql/issues/704>`__)
+- Introduce Typed config dict (`#706 <https://github.com/dbfixtures/pytest-postgresql/issues/706>`__)
+- Use ankane/setup-postgres@v1 to setup postgresql in CI instead of custom scripts. (`#708 <https://github.com/dbfixtures/pytest-postgresql/issues/708>`__)
+- Pass codecov_token to codecov action to upload coverage. (`#721 <https://github.com/dbfixtures/pytest-postgresql/issues/721>`__)
+- Replaced flake8 and pydocstyle with ruff, turned on isort rules (`#735 <https://github.com/dbfixtures/pytest-postgresql/issues/735>`__)
+- Split single bid test job into smaller running each after another. (`#740 <https://github.com/dbfixtures/pytest-postgresql/issues/740>`__)
 
 
 4.1.1
@@ -174,7 +243,7 @@ Misc
 
 - Error message typo fix
 - Docker documentation example typo fixes
-- Have setuptools required as package dependency. pkg_resources.parse_version is used in code 
+- Have setuptools required as package dependency. pkg_resources.parse_version is used in code
   but setuptools was only used as build requirements
 
 4.1.0
@@ -314,7 +383,7 @@ Bugfix
 2.6.0
 =====
 
-- [enhancement] add ability to pass options to pg_ctl's -o flag to send arguments to the underlying postgres executable 
+- [enhancement] add ability to pass options to pg_ctl's -o flag to send arguments to the underlying postgres executable
   Use `postgres_options` as fixture argument, `--postgresql-postgres-options` as pytest starting option or
   `postgresql_postgres_options` as pytest.ini configuration option
 
@@ -364,7 +433,7 @@ Bugfix
 =====
 
 - [feature] Allow to set password for postgresql. Use it throughout the flow.
-- [bugfix] Default Janitor's connections to postgres database. When using custom users, 
+- [bugfix] Default Janitor's connections to postgres database. When using custom users,
   postgres attempts to use user's database and it might not exist.
 - [bugfix] NoopExecutor connects to read version by context manager to properly handle cases
   where it can't connect to the server.
@@ -399,7 +468,7 @@ Bugfix
 1.4.1
 =====
 
-- [bugfix] Allow creating test database with hyphens 
+- [bugfix] Allow creating test database with hyphens
 
 1.4.0
 =====

{pytest_postgresql-6.1.1 → pytest_postgresql-7.0.1}/CONTRIBUTING.rst

@@ -19,7 +19,13 @@ Feature requests/proposals
 #. Provide as detailed description as possible
     * Use case is great to have
 #. There'll be a bit of discussion for the feature. Don't worry, if it is to be accepted, we'd like to support it, so we need to understand it thoroughly.
-  
+
+Development
+-----------
+
+#. Fork the repository
+#. Clone the repository
+#. Create a virtual environment with ``pipenv install --dev``
 
 Pull requests
 -------------
@@ -40,13 +46,17 @@ Commits
 Coding style
 ------------
 
-#. Coding style is being handled by black and doublechecked by flake8 and pydocstyle
+#. Coding style is being handled by black and doublechecked by ruff.
     * We provide a `pre-commit <https://pre-commit.com/>`_ configuration for invoking these on commit.
 
 Testing
 -------
 
-# Tests are written using pytest.
-# PR tests run on Github Actions.
-# In order to run the tests locally you need to have one version of postgres installed. And pass envvar named `POSTGRES` with used version number
-# If you encounter any test failures due to locale issues, make sure that both `en_US.UTF-8` and `de_DE.UTF-8` are enabled in `/etc/locale.gen` and then run `sudo locale-gen`.
+#. Tests are written using `pytest <https://docs.pytest.org/>`_
+#. PR tests run on Github Actions.
+#. Run a PostgreSQL server [#]_, and create a default super user ``createuser --superuser postgres``
+#. Set envvar named ``POSTGRES`` with used version number
+#. Run tests with ``pipenv run pytest``
+#. If you encounter any test failures due to locale issues, make sure that both ``en_US.UTF-8`` and ``de_DE.UTF-8`` are enabled in ``/etc/locale.gen`` and then run ``sudo locale-gen``.
+
+.. [#] Installing and configuring a PostgreSQL server is out of scope of this document. Please refer to `PostgreSQL documentation <https://www.postgresql.org/docs/>`_ for more information.

{pytest_postgresql-6.1.1 → pytest_postgresql-7.0.1}/COPYING

@@ -671,4 +671,4 @@ into proprietary programs.  If your program is a subroutine library, you
 may consider it more useful to permit linking proprietary applications with
 the library.  If this is what you want to do, use the GNU Lesser General
 Public License instead of this License.  But first, please read
-<http://www.gnu.org/philosophy/why-not-lgpl.html>.
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.

{pytest_postgresql-6.1.1 → pytest_postgresql-7.0.1}/COPYING.lesser

@@ -162,4 +162,4 @@ General Public License ever published by the Free Software Foundation.
 whether future versions of the GNU Lesser General Public License shall
 apply, that proxy's public statement of acceptance of any version is
 permanent authorization for you to choose that version for the
-Library.
+Library.

{pytest_postgresql-6.1.1 → pytest_postgresql-7.0.1}/PKG-INFO

@@ -1,11 +1,11 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.2
 Name: pytest-postgresql
-Version: 6.1.1
+Version: 7.0.1
 Summary: Postgresql fixtures and fixture factories for Pytest.
 Author-email: Grzegorz Śliwiński <fizyk+pypi@fizyk.dev>
-Project-URL: Source, https://github.com/ClearcodeHQ/pytest-postgresql
-Project-URL: Bug Tracker, https://github.com/ClearcodeHQ/pytest-postgresql/issues
-Project-URL: Changelog, https://github.com/ClearcodeHQ/pytest-postgresql/blob/v6.1.1/CHANGES.rst
+Project-URL: Source, https://github.com/dbfixtures/pytest-postgresql
+Project-URL: Bug Tracker, https://github.com/dbfixtures/pytest-postgresql/issues
+Project-URL: Changelog, https://github.com/dbfixtures/pytest-postgresql/blob/v7.0.1/CHANGES.rst
 Keywords: tests,pytest,fixture,postgresql
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Environment :: Web Environment
@@ -15,30 +15,30 @@ Classifier: Natural Language :: English
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.8
 Classifier: Programming Language :: Python :: 3.9
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
 Classifier: Programming Language :: Python :: 3 :: Only
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Classifier: Topic :: Software Development :: Testing
 Classifier: Framework :: Pytest
-Requires-Python: >=3.8
+Requires-Python: >=3.9
 Description-Content-Type: text/x-rst
 License-File: COPYING
 License-File: COPYING.lesser
 License-File: AUTHORS.rst
 Requires-Dist: pytest>=6.2
 Requires-Dist: port-for>=0.7.3
-Requires-Dist: mirakuru
-Requires-Dist: setuptools
+Requires-Dist: mirakuru>=2.6.0
+Requires-Dist: packaging
 Requires-Dist: psycopg>=3.0.0
 
-.. image:: https://raw.githubusercontent.com/ClearcodeHQ/pytest-postgresql/master/logo.png
+.. image:: https://raw.githubusercontent.com/dbfixtures/pytest-postgresql/master/logo.png
     :width: 100px
     :height: 100px
-    
+
 pytest-postgresql
 =================
 
@@ -122,38 +122,25 @@ Sample test
         postgresql.commit()
         cur.close()
 
-If you want the database fixture to be automatically populated with your schema there are two ways:
+Pre-populating the database for tests
+-------------------------------------
 
-#. client fixture specific
-#. process fixture specific
+If you want the database fixture to be automatically pre-populated with your schema and data, there are two lewels you can achieve it:
 
-Both are accepting same set of possible loaders:
+#. per test in a client fixture, by an intermediary fixture between client and your test (or other fixtures)
+#. per session in a process fixture
 
-* sql file path
-* loading function import path (string)
-* actual loading function
+The process fixture accepts a load parameter, which accepts these loaders:
 
-That function will receive **host**, **port**, **user**, **dbname** and **password** kwargs and will have to perform
-connection to the database inside. However, you'll be able to run SQL files or even trigger programmatically database
-migrations you have.
+* sql file path - which will load and execute sql files
+* loading functions - either by string import path, actual callable.
+  Loading functions will receive **host**, **port**, **user**, **dbname** and **password** arguments and will have to perform
+  connection to the database inside. Or start session in the ORM of your choice to perform actions with given ORM.
+  This way, you'd be able to trigger ORM based data manipulations, or even trigger database migrations programmatically.
 
-Client specific loads the database each test
-
-.. code-block:: python
-
-    from pathlib import Path
-    postgresql_my_with_schema = factories.postgresql(
-        'postgresql_my_proc',
-        load=[Path("schemafile.sql"), Path("otherschema.sql"), "import.path.to.function", "import.path.to:otherfunction", load_this]
-    )
-
-.. warning::
-
-    This way, the database will still be dropped each time.
-
-
-The process fixture performs the load once per test session, and loads the data into the template database.
-Client fixture then creates test database out of the template database each test, which significantly **speeds up the tests**.
+The process fixture pre-populates the database once per test session (at the start of the process fixture),
+and loads the schema and data into the template database. Client fixture then creates test database out of the template database each test,
+which significantly **speeds up the tests**.
 
 .. code-block:: python
 
@@ -162,14 +149,15 @@ Client fixture then creates test database out of the template database each test
         load=[Path("schemafile.sql"), Path("otherschema.sql"), "import.path.to.function", "import.path.to:otherfunction", load_this]
     )
 
+Additional benefit, is that test code might safely use separate database connection, and can safely test it's behaviour with transactions and rollbacks,
+as tests and code will work on separate database connections.
+
+Defining pre-populate on command line:
 
 .. code-block:: sh
 
     pytest --postgresql-populate-template=path.to.loading_function --postgresql-populate-template=path.to.other:loading_function --postgresql-populate-template=path/to/file.sql
 
-
-The loading_function from example will receive , and have to commit that.
-
 Connecting to already existing postgresql database
 --------------------------------------------------
 
@@ -222,6 +210,12 @@ You can pick which you prefer, but remember that these settings are handled in t
      - postgresql_port
      - yes (5432)
      - random
+   * - Port search count
+     -
+     - --postgresql-port-search-count
+     - postgresql_port_search_count
+     - -
+     - 5
    * - postgresql user
      - user
      - --postgresql-user
@@ -270,6 +264,18 @@ You can pick which you prefer, but remember that these settings are handled in t
      - postgresql_options
      - yes
      -
+   * - Drop test database on start.
+
+       .. warning::
+
+           Use carefully as it might lead to unexpected results within your test suite.
+     -
+     - --postgresql-drop-test-database
+     -
+     - false
+     -
+
+
 
 
 Example usage:
@@ -385,11 +391,11 @@ For this import DatabaseJanitor and use its init and drop methods:
         # variable definition
 
         janitor = DatabaseJanitor(
-            postgresql_proc.user,
-            postgresql_proc.host,
-            postgresql_proc.port,
-            "my_test_database",
-            postgresql_proc.version,
+            user=postgresql_proc.user,
+            host=postgresql_proc.host,
+            proc=postgresql_proc.port,
+            testdb="my_test_database",
+            version=postgresql_proc.version,
             password="secret_password",
         )
         janitor.init()
@@ -414,11 +420,11 @@ or use it as a context manager:
         # variable definition
 
         with DatabaseJanitor(
-            postgresql_proc.user,
-            postgresql_proc.host,
-            postgresql_proc.port,
-            "my_test_database",
-            postgresql_proc.version,
+            user=postgresql_proc.user,
+            host=postgresql_proc.host,
+            port=postgresql_proc.port,
+            dbname="my_test_database",
+            version=postgresql_proc.version,
             password="secret_password",
         ):
             yield psycopg2.connect(