Issue description

When the environment variable PIPENV_SITE_PACKAGES is set, pipenv always recreate new virtualenv on each invoke of pipenv even if it is not a pipenv install command.

Expected result

• pipenv run or pipenv shell should use existing virtualenv instead of creating a new one.
• PIPENV_SITE_PACKAGES should only affect pipenv install command.

Actual

This is a great issue to work on if you are new to the Poetry code base and want to start contributing. Over the years the poetry code base has added various fixes that catered to now unsupported versions of python. With the release of 1.2, we will drop support for all Python versions prior to 3.6. With this we want to clean up the code base of any such workarounds we did to support backwards

Current Behavior

UMD build doesn't support code-splitting and dynamic imports (rollup/rollup#3490, rollup/rollup#3491) due to Rollup current limitations, and tsdx cli don't accept the format option amd when creating build config

Suggested Solution

Consider support AMD module format, o

What's the problem this feature will solve?
I want to use pip to download linux packages onto a mac.

I know that I need to use some combination of --platform, --python-version, --only-binary=:all:. but I don't know the proper values for these options.

Describe the solution you'd like
I would like the documentation from the command line tool to be clear, or the package docum

Trying to --appimage-extract-and-run a x86_64 Linux AppImage on FreeBSD 12.1-RELEASE-p8 with the Linux compatibility layer:

user@FreeBSD$  /home/user/Downloads/Akira-26-x86_64.AppImage --appimage-extract-and-run
mkdir_p error: Permission denied
Failed to extract AppImage

but

user@FreeBSD$  /home/user/Downloads/Akira-26-x86_64.AppImage --appimage-extract

Issue Description

When reviewing a SR in the web UI, reviewers can either "Approve" or "Disregard" the SR. However, the word "disregard" is imo misused in this context, given the definition for disregard: to pay no attention to; treat as unworthy of regard or notice. Actually though, the reviewer is paying enough attention to the SR to

Currently, metadata is read from Cargo.toml's [package] and [package.metadata.maturin]. Now with PEP 621, this should be moved to the standardized pyproject.toml [project] instead.

For the implementation, it should still be checked whether [package.metadata.maturin] exists and users should be told that this is deprecated and that they should