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
The reports module is sort of disconnected from the rest of pybids, and I was thinking that it might be a good idea to move it to its own package (e.g., bids-standard/pybids-reports). I brought this idea up in today's BIDS maintainers meeting, and our decision was to open an issue to give users the opportunity to weigh in on this idea.
A bit of context:
The only dependency that reports currently adds is num2words, but @Remi-Gau has proposed using a templating tool to build reports in the future.
AFAIK, the reports module is not commonly used, so I assume that removing it from pybids won't cause any major problems for users. Please feel to comment here if that's not the case.
Any new library would use pybids as a dependency.
The text was updated successfully, but these errors were encountered:
Would it make sense to do it as a namespace package, so it would still be imported as bids.reports? This is how we're doing pydra task packages which get imported under pydra.tasks.<package>.
We might be able to do something clever on our end, so that attempting to import without the package installed raises an informative error:
>>>frombidsimportreportsImportError("Please install the pybids-reports package with pip")
That should help smooth out any transition, especially if you're able to maintain the API for a few versions at least.
The
reports
module is sort of disconnected from the rest ofpybids
, and I was thinking that it might be a good idea to move it to its own package (e.g.,bids-standard/pybids-reports
). I brought this idea up in today's BIDS maintainers meeting, and our decision was to open an issue to give users the opportunity to weigh in on this idea.A bit of context:
reports
currently adds isnum2words
, but @Remi-Gau has proposed using a templating tool to build reports in the future.reports
module is not commonly used, so I assume that removing it frompybids
won't cause any major problems for users. Please feel to comment here if that's not the case.pybids
as a dependency.The text was updated successfully, but these errors were encountered: