`python-venv.sh` script doesn't work with multiple sub directories

[mfts]

I'm packging azure-cli and ran into the issue that they have different subdirectories here: https://github.com/Azure/azure-cli/tree/dev/src

[mxcl]

The new bkpyvenv supports this to some extent. Hard to be sure though since I'm not sure from the report if the issue is that two virtual-environments are needed or if multiple commands need to be provided.

[magnusviri]

I don't know if this is related but I ran into an issue with a project named jctl with the error error: Multiple top-level packages discovered in a flat-layout: ['jctl', 'props']. I had to add something to my setup.py file to get around it. https://stackoverflow.com/questions/72294299/multiple-top-level-packages-discovered-in-a-flat-layout

[jhheider]

@magnusviri that sounds like it doesn't like the props directory pkgx makes; if you have no props, considering rmdir props or mv props .props and see if it like that better.

[mxcl]

we could probably deprecate props and use the new per array node prop in general since adding files to a build directory is asking for issues like @magnusviri’s

[jhheider]

it's true; the only argument against it is potential bloat in the yaml reducing legibility. possibly only creating the props directory if needed will give the yaml author the control they need.

inlining long/ugly patches doesn't sound fun.

[mxcl]

we could allow the prop: node to take a filename

[jhheider]

well, if we're brainstorming, we could have an build.script[].install { dest, contents, mode? } key, if we needed to keep it "simple".