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
Because development activity seems to be slightly increasing here (#8, #9), I was wondering what the plans for the future are, especially with respect to PR #7. As #7 is a major rewrite of central parts it seems that it might be wasted effort to implement a lot of new features on the current master branch if the intend is to transition to that approach. It certainly adds complexity, but also increases the flexibility.
I will use #7 as part of my projects for sure and it would be nice to be able to link to it and pip install it easily (which is problematic if it lives in this branch). So if there is no intend to get this merged into ctn_benchmarks, I might go ahead and transition the code from the PR to its own repository.
Another point is that I think that #4 should be resolved earlier than later. The larger the user-base, the more problematic such fundamental changes as renaming the package will get.
The text was updated successfully, but these errors were encountered:
Because development activity seems to be slightly increasing here (#8, #9), I was wondering what the plans for the future are, especially with respect to PR #7. As #7 is a major rewrite of central parts it seems that it might be wasted effort to implement a lot of new features on the current master branch if the intend is to transition to that approach. It certainly adds complexity, but also increases the flexibility.
I will use #7 as part of my projects for sure and it would be nice to be able to link to it and pip install it easily (which is problematic if it lives in this branch). So if there is no intend to get this merged into ctn_benchmarks, I might go ahead and transition the code from the PR to its own repository.
Another point is that I think that #4 should be resolved earlier than later. The larger the user-base, the more problematic such fundamental changes as renaming the package will get.
The text was updated successfully, but these errors were encountered: