blitzmann
commented
2 years ago @rumline I'm assuming it's the same situation as #2373, you have incorrect versions of various libraries and packages used by pyfa. Please use a virtual env and install the requirements as noted in the requirements.txt file in the root of the repo.
If that doesn't work, please reply. Thanks!
Bug Report
Running 2.38.1 from a "git clone" on Windows. On startup of pfya.py, many warning messages are displayed.
Expected behavior:
No warnings displayed
Actual behavior:
E:\Games\Pfya\service\market.py:263: SAWarning: relationship 'DynamicItem.applicableItems' will copy column mutaplasmids.typeID to column mutaplasmidItems.typeID, which conflicts with relationship(s): 'DynamicItemItem.mutaplasmid' (copies mutaplasmids.typeID to mutaplasmidItems.typeID). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="mutaplasmid"' to the 'DynamicItem.applicableItems' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) self.les_grp = types_Group() E:\Games\Pfya\service\market.py:263: SAWarning: relationship 'Item.mutaplasmids' will copy column mutaplasmids.typeID to column mutaplasmidItems.typeID, which conflicts with relationship(s): 'DynamicItemItem.mutaplasmid' (copies mutaplasmids.typeID to mutaplasmidItems.typeID). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="mutaplasmid"' to the 'Item.mutaplasmids' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) self.les_grp = types_Group() E:\Games\Pfya\service\market.py:263: SAWarning: relationship 'Fit._Fitmodules' will copy column fits.ID to column modules.fitID, which conflicts with relationship(s): 'Module.owner' (copies fits.ID to modules.fitID). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="owner"' to the 'Fit._Fitmodules' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) self.les_grp = types_Group() E:\Games\Pfya\service\market.py:263: SAWarning: relationship 'Fit._FitprojectedModules' will copy column fits.ID to column modules.fitID, which conflicts with relationship(s): 'Fit._Fitmodules' (copies fits.ID to modules.fitID), 'Module.owner' (copies fits.ID to modules.fitID). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="_Fitmodules,owner"' to the 'Fit._FitprojectedModules' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) self.les_grp = types_Group() E:\Games\Pfya\service\market.py:263: SAWarning: relationship 'Fit._Fitboosters' will copy column fits.ID to column boosters.fitID, which conflicts with relationship(s): 'Booster.owner' (copies fits.ID to boosters.fitID). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="owner"' to the 'Fit._Fitboosters' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) self.les_grp = types_Group() E:\Games\Pfya\service\market.py:263: SAWarning: relationship 'Fit._Fitdrones' will copy column fits.ID to column drones.fitID, which conflicts with relationship(s): 'Drone.owner' (copies fits.ID to drones.fitID). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="owner"' to the 'Fit._Fitdrones' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) self.les_grp = types_Group() E:\Games\Pfya\service\market.py:263: SAWarning: relationship 'Fit._Fitfighters' will copy column fits.ID to column fighters.fitID, which conflicts with relationship(s): 'Fighter.owner' (copies fits.ID to fighters.fitID). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="owner"' to the 'Fit._Fitfighters' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) self.les_grp = types_Group() E:\Games\Pfya\service\market.py:263: SAWarning: relationship 'Fit._Fitcargo' will copy column fits.ID to column cargo.fitID, which conflicts with relationship(s): 'Cargo.owner' (copies fits.ID to cargo.fitID). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="owner"' to the 'Fit._Fitcargo' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) self.les_grp = types_Group() E:\Games\Pfya\service\market.py:263: SAWarning: relationship 'Fit._FitprojectedDrones' will copy column fits.ID to column drones.fitID, which conflicts with relationship(s): 'Drone.owner' (copies fits.ID to drones.fitID), 'Fit._Fitdrones' (copies fits.ID to drones.fitID). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="_Fitdrones,owner"' to the 'Fit._FitprojectedDrones' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) self.les_grp = types_Group() E:\Games\Pfya\service\market.py:263: SAWarning: relationship 'Fit._FitprojectedFighters' will copy column fits.ID to column fighters.fitID, which conflicts with relationship(s): 'Fighter.owner' (copies fits.ID to fighters.fitID), 'Fit._Fitfighters' (copies fits.ID to fighters.fitID). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="_Fitfighters,owner"' to the 'Fit._FitprojectedFighters' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) self.les_grp = types_Group()