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
xnd-all is a convenience package. All packaging should IMO be in the individual libraries.
I would need more information a) what would be improved and b) how to make conda play well with subtrees(!).
Also, I would encourage people to use python3 setup.py develop without conda for developing. It is faster and has cleaner output (no _placehold/_placehold/...).
All packaging should IMO be in the individual libraries.
Actually I think the packaging for individual libraries is good, I mean, it would be better if each library build its own package. this workflow is more agil than make a PR in the library repo waiting for merge, update the xnd-all, make a PR and waiting for merge.
I would need more information a) what would be improved and b) how to make conda play well with subtrees(!).
actually I suggest to move the .conda just to avoid need to make a PR into 2 repos for packaging story. but I think if each library build its own package that would be better (eg. for xndtools the user just need to make the PR into xndtools ... and after merging that will create the package for xndtools).
Also, I would encourage people to use python3 setup.py develop without conda for developing. It is faster and has cleaner output (no _placehold/_placehold/...).
Maybe would be good to have the .conda just on xnd-all that would help to improve the current workflow.
In our last doc meeting we talked that would be better to have the packaging of [lib]ndtypes separated from xnd-all
The text was updated successfully, but these errors were encountered: