There is PBPharoPlatform>>#copyApplicationTo:application:, which copies the whole PythonBridge folder, including the Pipfile. It seems essential to real use to be able to specify one's own Pipfile, but it's difficult to see how to do that. It seems maybe PBPharoPlatform is trying to do too much. This logic doesn't seem to be specific to the "Pharo platform".
I thought maybe the Platform was a facade for the low-level support libraries like FileSystem and OSSSubprocess, but I see not because there is:
PBApplication>>#workingDirectory
^ settings workingDirectory ifNil:
[ FileLocator imageDirectory / self runtimeDirectory ]
Pipfile specification should be delegated back to PBApplication and maybe there are other interesting customization points?
There is
PBPharoPlatform>>#copyApplicationTo:application:, which copies the wholePythonBridgefolder, including the Pipfile. It seems essential to real use to be able to specify one's own Pipfile, but it's difficult to see how to do that. It seems maybePBPharoPlatformis trying to do too much. This logic doesn't seem to be specific to the "Pharo platform".I thought maybe the Platform was a facade for the low-level support libraries like FileSystem and OSSSubprocess, but I see not because there is:
Pipfile specification should be delegated back to PBApplication and maybe there are other interesting customization points?