You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at PyPackage.Manager.Pip.pas and cross-referencing with PythonEnvironments' PyTools.ExecCmd.pas there are methods defined to capture IO but these are unused as everything calls the Run(AOutput) version
It seems desirable to use the capture if a (unimplemented) PIP/Conda IO event were available. This would possibly allow the use of the Progress option to monitor what the install was doing. This would be especially useful for very large packages (e.g. Torch-GPU takes 4 mins to download with no way to inform the user what's going on)
The text was updated successfully, but these errors were encountered:
From looking at what PIP does it shows a progress bar when installing a new module.
This is displayed on one line being overwritten periodically looking like this...
Yoiu might need to "pip uninstall torch" and possibly "pip cache purge" to get a proper idea of the issue.
What I'm hoping is that the last line can be parsed to return some useful info on install progress in the 5 mins 36 secs mine says it's taking. This could then be used to drive a Delphi progress bar etc.
While I'm using an extreme example here this also applies to smaller packages - it just isn't quite as bad as this case...
A lot of ML Python stuff relies on large quantities of data - I mean CoCo 2017 (117k training images) is 18Gb for example. Those I can handle as it's just files from the Internet but PIP has no mechanism for developer-friendly progress information.
Looking at PyPackage.Manager.Pip.pas and cross-referencing with PythonEnvironments' PyTools.ExecCmd.pas there are methods defined to capture IO but these are unused as everything calls the Run(AOutput) version
It seems desirable to use the capture if a (unimplemented) PIP/Conda IO event were available. This would possibly allow the use of the Progress option to monitor what the install was doing. This would be especially useful for very large packages (e.g. Torch-GPU takes 4 mins to download with no way to inform the user what's going on)
The text was updated successfully, but these errors were encountered: