Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move .conda from libraries to xnd-all #19

Open
xmnlab opened this issue Aug 15, 2018 · 2 comments
Open

Move .conda from libraries to xnd-all #19

xmnlab opened this issue Aug 15, 2018 · 2 comments

Comments

@xmnlab
Copy link
Member

xmnlab commented Aug 15, 2018

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

@skrah
Copy link
Member

skrah commented Aug 15, 2018

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/...).

@xmnlab
Copy link
Member Author

xmnlab commented Aug 16, 2018

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/...).

great! we could put that into the docs!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants