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
Running the Excel UI from the command line (i.e., python -m FlowCal.excel_ui -v -p -i experiment.xlsx) with Python 3 throws a RuntimeWarning that could alarm users.
This warning is well described by this Stack Overflow post—the excel_ui module is getting imported twice when invoked with python -m. This shouldn't be a problem for FlowCal because it doesn't store state in the excel_ui module, but the warning could alarm or annoy users.
A solution recommended in this Stack Overflow answer is to separate the module from its command line interface. E.g., python -m FlowCal.excel_ui_cli -v -p -i experiment.xlsx. The new interface would not be backwards compatible, though. To address this, the answer suggests keeping the old interface and throwing a deprecation warning, which seems reasonable to me.
Another option is to silence the warning (per this Stack Overflow answer), but I'd prefer not to do that if there's a better alternative.
The text was updated successfully, but these errors were encountered:
Running the Excel UI from the command line (i.e.,
python -m FlowCal.excel_ui -v -p -i experiment.xlsx
) with Python 3 throws aRuntimeWarning
that could alarm users.This warning is well described by this Stack Overflow post—the
excel_ui
module is getting imported twice when invoked withpython -m
. This shouldn't be a problem for FlowCal because it doesn't store state in theexcel_ui
module, but the warning could alarm or annoy users.A solution recommended in this Stack Overflow answer is to separate the module from its command line interface. E.g.,
python -m FlowCal.excel_ui_cli -v -p -i experiment.xlsx
. The new interface would not be backwards compatible, though. To address this, the answer suggests keeping the old interface and throwing a deprecation warning, which seems reasonable to me.Another option is to silence the warning (per this Stack Overflow answer), but I'd prefer not to do that if there's a better alternative.
The text was updated successfully, but these errors were encountered: