packaging

I am trying out the latest version (from the master branch) to find out if some earlier issues are fixed, but I stumble upon something else.

When installing some dependencies (in my case numpydoc==0.8.0 and overrides==1.9), this fail with the message Will try again. Indeed, pipenv lets me know 'Installing initially failed dependencies...' but does not give any feedback whether it succeede

• I am on the latest Poet

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

Description

If you run pip config --edit with an editor that doesn't exist, pip presents a traceback.

Expected behavior

pip would present a clear error message, about which file could not be found.

pip version

21.3.1

Python version

N/A

OS

Windows

How to Reproduce

Run pip config edit --editor code on a Windows machine without VSCode ins

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

If a mirror just contains source packages, aptly is not able to update it.

aptly always expects that there are binary packages on the mirror.

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?

Adding an non existing project to a "_meta" file leads to 500.

How to reproduce it:

• Open a "meta" file from a page
• Add an non existing project to as path
• Save the file

i.e:

  <repository name="openSUSE_15.2">
    <path project="foo:bar" repository="openSUSE_15.2"/>
    <arch>x86_64</arch>
    <arch>armv7l</arch>
    <arch>aarch64</arch>
    <arch>ppc64le</arch>
  </rep