continue uploading further packages using --fromdir if a package 'excepts' for some reason about devpi

[devpi-bot]

Original comment by @hpk42

It should always do appropriate logging, however. And "generic" exception catching is a critical. Let's rather look at exactly goes wrong and report about the case.

[devpi-bot]

Original comment by @AvdN

If you have a directory with old stuff downloaded from PYPI, then I expect upload to upload anything it can and skip the rest.
Why some packages are not handled by pkginfo is e.g.:

• No PKG-INFO in archive [ rst2pdf-0.92, rst2pdf-0.16, docutils-0.9, dulwich 0.8.6, eyeD3, rdiff-backup, html5lib, uwsgi]
• Not a known archive format: [ various .egg files: Extremes, pylint 0.18, WebOb, DecoratorTools]
  Maybe the No PKG Info should be handled differently and should the .egg files not be offered to pkginfo at all (I got the idea they all fail to be uploaded).
  Is there already a unitttest for uploading that downloads a set of files and tries to upload them?

[devpi-bot]

Original comment by @hpk42

It seems we just need to use pkginfo.get_metadata which will also read egg files correctly (i used pkginfo.SDist which is too specific, there also is pkginfo.BDist etc. and the get_metadata is the generic entry point it seems) . As for the remaining packages which don't have a PKG-INFO we can fallback to parse the filename to obtain name/version info. This is enough for devpi's "submit" action.

Are you up for a little PR doing this?

[devpi-bot]

Original comment by @AvdN

I will do that ( I Have the material to test ;-) )

[devpi-bot]

Original comment by @hpk42

resolve issue3 - also print an error message in case we don't find a PKGINFO file.

→ <>

[devpi-bot]

Original comment by @hpk42

automatically start server for install and other commands, fixes issue3

→ <>