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

Investigate Integrating Toolz #14

Closed
EntilZha opened this issue Mar 16, 2015 · 3 comments
Closed

Investigate Integrating Toolz #14

EntilZha opened this issue Mar 16, 2015 · 3 comments
Assignees
Labels
Milestone

Comments

@EntilZha
Copy link
Owner

Via Twitter got suggested to checkout toolz. I think its worth looking into as powering part of the backend. It may help clean up code, make certain things easier to extend, and improve performance.

I've posted to their mailing list expressing interest in collaboration.

@EntilZha EntilZha self-assigned this Mar 16, 2015
@EntilZha
Copy link
Owner Author

Can add these projects to look at as well:

fn.py

Funcy

@EntilZha EntilZha added this to the 0.4.0 milestone May 9, 2015
@EntilZha
Copy link
Owner Author

EntilZha commented May 9, 2015

Thinking perhaps theme of 0.4.0 will be bringing in some utility things from other libraries and/or iterop with other formats, so marking this for 0.4.0

@EntilZha
Copy link
Owner Author

Looking at these, the one with the most potential to benefit from is the _ operator from fn.py. Most of the other things are either already in functional, or could be added. It also is hard to use them as underlying engines since there is already a custom pipelining engine.

Therefor, fn.py has been added as a dependency and is importable via from functional import _. The intent is that the only import required is from functional import seq, _. This was done in a009a67 and fixes for build issues in subsequent commits.

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

No branches or pull requests

1 participant