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
tcy currently requires the user to have a "necessity" column in the .tsv file. This was introduced primarily because the github runners did not have enough RAM in the past to solve .yml files with too many packages. However, RAM for the runners was increased in the last year. Pitching for adapting this argument, so that tcy can accept any other key-value(s) pair where the key represents a column and the value(s) represent rows that should be filtered for. This gives more flexibility to the users.
**kwargs could also be named **filter_kwargs or something
The text was updated successfully, but these errors were encountered:
The first one would mean that for this column we only want rows that have any of these values and the second one would mean that we only want to include rows where this column only has this value
tcy currently requires the user to have a "necessity" column in the .tsv file. This was introduced primarily because the github runners did not have enough RAM in the past to solve .yml files with too many packages. However, RAM for the runners was increased in the last year. Pitching for adapting this argument, so that tcy can accept any other key-value(s) pair where the key represents a column and the value(s) represent rows that should be filtered for. This gives more flexibility to the users.
**kwargs could also be named **filter_kwargs or something
The text was updated successfully, but these errors were encountered: