For now we're thinking this generates too much noise -- we'll add it
back as we approach 3.11 RCs

After digging around in the poetry code to figure out
how to include an `extras` key in a CLI script,
I thought it might be a useful thing to add to the docs
for future users.

Export requirements.txt without index URLs

Co-authored-by: DBM012 <dustin.moriarty@amfam.com>

get() is a function and not an object with __enter__ (aka context manager)

When a project specifies a narrow range for the supported python
versions, i.e. "python ~= 3.6.1" and the current interpreter falls
outside of that range, the fallback code fails to test an available
python3.6 interpreter because of a too strict a test.

Relates to: #2153
When running `poetry update`, during the download phase when `PYTHONWARNINGS="default"` environment variable is set, multiple different sessions trigger resource warnings. This fixes one of them that occurs during the download phase of the package update.

```
/Users/username/Library/Application Support/pypoetry/venv/lib/python3.10/site-packages/poetry/installation/executor.py:594: ResourceWarning: unclosed <ssl.SSLSocket fd=5, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('REDACTED', 59025), raddr=('140.108.3.33', 80)>
```

This line references:
```
 593   │             try:
 594   │                 archive = self._download_archive(operation, link)
 595   │             except BaseException:
 596   │                 cache_directory = self._chef.get_cache_directory_for_link(link)
```

The issue is being caused because the session is being left open when the class is later cleaned up. By adding a destructor method, we can close the session if it exists, preventing this error.

test_env_shell_commands_with_stdinput_in_their_arg_work_as_expected contains path comparison which does not take into account potential symlinks.
When testing under MacOS and brew-installed python, venv version points to a path with symlink while python outputs the resolved path.

Co-authored-by: Arun Babu Neelicattu <arun.neelicattu@gmail.com>
Co-authored-by: Bjorn Neergaard <bjorn@neersighted.com>

The `debug resolve` had an extra row included in its table, adding extra
whitespace. Also, remove a list that is discarded immediately.

code-quality.yaml / the `pre-commit` workflow are made a no-op to smooth
the transition.

* new FIXME: are nameless repositories desired/expected?

* new TODO: should the LegacyRepository really inherit from the PyPiRepository?

Resolves: #3412

Document a solution for using passwords that start with a dash. This happened to a few people when using automatically generated tokens in a CI environment.

Fixes #2889

Co-authored-by: Bjorn Neergaard <bjorn@neersighted.com>

Should help with cases like #3397

The existing tests in tests/publishing/test_uploader.py should verify
that this doesn't cause regressions.

Updated documentation for more specification about module and project names, due to ModuleOrPackagesNotFound uncertainty.

Co-authored-by: Steph Samson <hello@stephsamson.com>
Co-authored-by: Paul "TBBle" Hampson <Paul.Hampson@Pobox.com>

A lack of a rebase before merge kept this intersection of changes from
being properly tested.

* Adding a note about being able to specify a package's source repository

* Updating the list of options for the add command

fix(utils.patterns): version part in filename must be present according PEP491

Locker will set package.source_url relative to lock path, this
made it so that tests were failing if run outside root directory
because lock path was set to Path(__file__).

With using project_root fixture as lock path now tests can be run
from any directory.