Relates-to: python-poetry/poetry#3132
Relates-to: python-poetry/poetry#3200

This change allows for development dependencies to be ignored creating
`Poetry` instances. This is used when PEP 517 artifacts are built as 
they are not required in this scenario.

Relates-to: python-poetry/poetry#2174

Ref: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

Fixes https://github.com/python-poetry/poetry-core/issues/110

* Simplify temporary_directory and use safe_rmtree

Related to python-poetry/poetry#3545

This resolves a crash that occurs on PyPy3 on Windows

Closes python-poetry/poetry#3545

Paths for generated code that's excluded by vcs, but then included
explicitly, were wrong because they appared in the exclude list during
Builder.find_excluded_files(). I changed find_excluded_files to not
exclude files which are explicitly included, by taking a set difference.

Added a test for this case.

Useful for R&D departments :) 
python-poetry/poetry#3485

Update packaging dep to v20.8

Fix #3285

Always close the wheel tempfile after writing to it

Make sdist deterministic by setting gzip mtime to 0

…-hinting

fix incorrect type hints and add missing ones

python-poetry#127)

Fixes python-poetry/poetry#2271

…try#129)

Release 1.0.1

…ython-poetry#134)

Release 1.0.2

* Update CI files for Python 3.6+ only

* Modernize codebase

* Reorganize imports to improve performance

The sync target previously regenerated the poetry.lock for vendored
packages, causing larger than necessary change set for patches. This
change introduces the update target to specifically handle lock file
updates, lock target to regenerate the lock file and repurpose the sync
target to only sync as expected.

Setting develop to `True` by default causes un-expected side-effects
and requires downstream consumers to rely on checks like
`package.develop and package.source_type == "directory""` to determine
if develop mode.

This also corresponds to current high-level behaviour of packages being
non-develop by default.

This is a broad change aligning `poetry.core.semver.version.Version`
implementation to be closer to PEP-440 that to semver. This adds the
foundation for improved dev and local tag support in poetry managed
version as well as fix ordering bugs that existed due to the
differences between semantic versioning specification and PEP-440.

Further, previously used inline copy of `packaging.version.Version`
implementation has now been removed in favour of
`poetry.core.version.pep440.PEP440Version` implementation.

We do this since poetry releases currently do not work with python
3.10.

This can be replaced once new bootstrap is available.

…poetry/poetry#3366

…ython-poetry/poetry#3366"

This reverts commit 28b7a07.

Release 1.1.0a1

* tests: fix incorrect parameters

* pep440: replace lark in favour of regex

The lark early implementation of PEP440 that was introduced was not
performant. The implementation added on average around 7 seconds to
the test suite execution time.

This change drops the lark parser, and uses `packaging.version`
provided regex for version string parsing. New dataclass interface for
version instances remain unaffected.

…etry#157)

* tests: add coverage for poetry.core.version.pep440

* pep440: allow release tuples

* pep440: support post/local release comparisons

This change ensures that post and local releases are taken into
consideration when checking if version range allows a post release
local build release at upper and lower bounds.

The following conditions now hold for upper bound checks.

- `<=3.0.0` allows `3.0.0+local.1`, `3.0.0-1`
- `<=3.0.0+local.1` disallows `3.0.0+local.2`, allows `3.0.0-1`
- `<=3.0.0-1` allows `3.0.0+local.1`, `3.0.0`

Lower bound checks require no modification and works due to the
implicit version comparison of `poetry.core.pep440.PEP440Version`.

This change ensures that post and local releases are taken into
consideration when checking if semver version instance allows
post and local build releases.

The following conditions now hold `poetry.core.semver.Version.allows`.

- `3.0.0` allows `3.0.0+local.1`, `3.0.0-1`
- `3.0.0+local.1` disallows `3.0.0+local.2`, allows `3.0.0-1`
- `3.0.0-1` disallows ``3.0.0`, `3.0.0+local.1`, allows `3.0.0-1+local.1`

Release 1.1.0a2

Release 1.1.0a3

Resolves: python-poetry/poetry#3705

This change also fixes python 3.10 failures.

When generating setup.py and PKG-INFO files, ensure that generated
files use a deterministic timestamp to enhance reproducibility of
source distributions.

…ies with markers (python-poetry#153)

* fix(packages/dependency): add space after filename for file dependencies with markers

local vendored files need a space after the file name and before the ";" which demarks the start of
markers

fix #3872

new (vcs.git): extract user credential (passord, deployment key, ...) from git url
change (vcs.git): change order of init arguments for `ParsedUrl`
change (vcs.git): make user, password, port, name and rev optional for `ParsedUrl`

…olean whether the ParsedUrl contains a secret like a password