packaging

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

We're doing a bunch of code quality cleanup, and as part of that effort I'd like to implement some additional lints/coding conventions. There will be a lot of manual changes here, so I think these will be some items to have multiple people tackle.

In no particular order:

• Add ban-relative-imports = true to .flake8 and remove relative imports from the repo.
• ~Add `flake8-type-checki

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

Would it make sense to have a logger.debug (or logger.info/warning) call here mentioning that the version couldn't be parsed ?

Originally posted by @xavfernandez in pypa/pip#10117 (comment)

Yes, let's do a warning. :)

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

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

I can configure to automatically run a command after the command pdm install.
Just like script "prepare" in npm.
This would be useful for new users init project, for example, I don't need

The maturin side of PyO3/setuptools-rust#112

Currently maturin has no sdist command, it builds sdist along with binary wheels. Do we want a seperated sdist command and add vendoring support to that, or do we want to directly add vendoring support to existing build command?

Github introduced a nice UI for syncing your fork with upstream.

We could use something like that for package links. osc has the setlinkrev command for this.