let's decompose the problem

• wppm supporting Drag & Drop of a pylock.toml file , understanding it as such by its prefix/postfix
• given current pip state

  • transform the pylock file into a requirement-with-hash file

  • create a WheelHouse directory

    • at WheelHouse/. the pylock file and the requirement-with-hash file
    • at subdirectory from pylock name, the target wheels

  • if no "default" Wheelhouse, download on confirmation from web into pylock subdirectory

  • otherwise download from "default" to same sub-directory

  • check wheels all there (errors management)

  • if yes install

so we need:

• end-user / wppm
  • Drag & Drop for the comfort use
  • a -ws --WheelSource option to specify where we look for wheels to install from, default=None or ./default if exists
  • a -wd --WheelDrain option to specify where we place wheels for install, default=None or ./default if exists
  • a check all there and right before applying
• build side:
  • use wppm to post-generate a default directory with wheels from another pylock file
    • generate slim version
    • generate wheel version:
      • like a dot version
      • then use pip lock with a big requirement to generate a reference pylock.www.toml
      • from wppm pylock.www.toml from feed included.wheels
      • then final zip