apipkg

• drop dead python versions
• migrate to hatch

• drop the python 3.4 support marker, 2.1.0 broke it 2.1.0 will be yanked after release

What's Changed

• Fix race condition for import of modules which use apipkg in Python 3.3+ by @GlenWalker in https://github.com/pytest-dev/apipkg/pull/27

Full Changelog: https://github.com/pytest-dev/apipkg/compare/v2.0.1...v2.1.0

• fix race conditions for attribute creation

• also transfer spec attribute
• make py.test hack more specific to avoid hiding real errors
• switch from Travis CI to GitHub Actions
• modernize package build
• reformat code with black

• switch to setuptools_scm
• move to github
• fix up python compat matrix
• avoid dict iteration (fixes issue on python3)
• preserve package - ths gets us better pep 302 compliance

• revert the automated version gathering

• fix issue2 - adapt tests on Jython
• handle jython pkgpath missabstraction when running python from jar files
• alias modules pointing to unimportable modules will return None for all their attributes instead of raising ImportError. This addresses python3.4 where any call to getframeinfo() can choke on sys.modules contents if pytest is not installed (because py.test.* imports it).
• introduce apipkg.distribution_version(name) as helper to obtain the current version number of a package from install metadata its used by default with the package name
• add an eagerloading option and eagerload automatically if bpython is used (workaround for their monkeypatching)

• Allow to import from Aliasmodules (thanks Ralf Schmitt)
• avoid loading doc early, so ApiModule is now fully lazy

• make apipkg memorize the absolute path where a package starts importing so that subsequent chdir + imports won't break.

• allow to alias modules

• allow to use dotted names in alias specifications (thanks Ralf Schmitt).