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

New version of this package #45

Open
ewengillies opened this issue Jun 14, 2019 · 9 comments
Open

New version of this package #45

ewengillies opened this issue Jun 14, 2019 · 9 comments

Comments

@ewengillies
Copy link

Hello devs,

This package has been a part of my workflow for several years now, mainly since I spend most of my time on the command line. I see its not really maintained anymore. I would like to take responsibility for it if no one minds, mostly so I can get it working with python 3 (and have this version on PyPI) and add some features.

If this sounds okay, I propose one of three ways to transition this (in order of my preference):

  1. I fork the package and keep the same name. In this scenario, I'd like access to the data_hacks package on PyPI so I can upload the python 3 version and keep it up-to-date.
  2. I fork the package and use a new name (e.g. data_hacks_3 or data_cli). This would be more like making my own package with this package as a starting point. In this scenario, I would just need your permission, I'll handle the rest.
  3. I offer my support to the main fork of the package. I think this solution would cause the most overhead for you all, so that's why I've listed this solution last.

Let me know which sounds best for you. Thanks!
Ewen

@mccarthyryanc
Copy link

@ewengillies , I've been waiting YEARS for updates to this repo. Given the level of responsiveness, I'd say you're better off going with option 2. No LICENSE file on the repo, but there is a license within the code comments. I'm not a lawyer, but If you carry that same license in a new repo (and refer back to this repo), I think you would be okay.

@fschaefer
Copy link

fschaefer commented Jul 16, 2019

@ewengillies I agree with @mccarthyryanc : the code is Apache licensed. Just find a proper name and go ahead with option 2 and fork the repository.

@ewengillies
Copy link
Author

@fschaefer and @mccarthyryanc, thanks for the advice. I had a bit more time a month ago, but I know I'll find time for this. I don't think it will be that much of an effort to do a python 3 port, hopefully I'll find time to revamp the code a bit and add some features. I'll update on this issue when I have a stable release.

@ewengillies
Copy link
Author

just as a quick poll, what features do you use from this package?

@mccarthyryanc
Copy link

@ewengillies , bar_chart and histogram are the main ones I use. Updating for Python3 was pretty simple on these utilities too. When you fork, I'd be happy to add some PRs with updates.

@tw-xren
Copy link

tw-xren commented Oct 6, 2020

Hi @ewengillies , Have you get a chance to work on option 2? I was thinking to make a python3 port for this tool recently and then find this issue. If not I can proceed if you don't have something that is already work in progress.

@ewengillies
Copy link
Author

@xiaojun-tw

It was a weekend project that never took off. Feel free to do the port, and keep us on this thread posted please! Let me know if I can help at all.

@mccarthyryanc
Copy link

While not an exact replacement, I've been using visidata in place of data_hacks. It does quite a lot and includes tools for statistics and histograms.

@nicholasren
Copy link

nicholasren commented Oct 8, 2020

Added python3 support and released at https://pypi.org/project/data-hacks3/

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

No branches or pull requests

5 participants