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

Package is not available on pypi #12

Open
olliebun opened this issue Aug 3, 2015 · 13 comments
Open

Package is not available on pypi #12

olliebun opened this issue Aug 3, 2015 · 13 comments

Comments

@olliebun
Copy link

olliebun commented Aug 3, 2015

I want to publish a package on pypi that depends on pydot.

As you're aware, the pypi package is unmaintained an out-of-date.

I briefly had my own fork and contacted the maintainer. He seemed willing to pass on ownership of the palckage, but the conversation never went beyond that.

IMO uploading the package under a different name (even pydot2) would be a good way forward.

@johnyf
Copy link

johnyf commented Aug 3, 2015

I think that such PyPI entries already exist:

I believe that preserving the name is important, in order to avoid unnecessary renames in code, over many packages.
The original googlecode page of pydot has been updated to forward to the original author's repository on github. So, an "official" repository exists on github. The next thing would be to:

  1. merge the changes collected here to upstream.
  2. find a maintainer for the PyPI entry.

I would be happy to do both, as I have had the same issue with pydot being an exception for pip. You mention that the PyPI owner appears willing to add a maintainer. So, there was just no further action in that direction ?

@olliebun
Copy link
Author

olliebun commented Aug 3, 2015

Yep, I agree with all of that.

I was in contact with Ero Carrera over email about adding a maintainer, he seemed happy with it, I followed up to ask about the next steps and he didn't get back to me. Definitely worth trying again. I can reach out again if you want - or leave it to you. This was about 18 months ago IIRC.

@peterjc
Copy link

peterjc commented Sep 28, 2015

+1 for someone taking over the existing PyPI entry and merging these Python 3 fixes.

@takluyver
Copy link

Yes, it would definitely be good to try to consolidate the different pydot forks and update the package on PyPI.

Pinging @ksambor and @prmtl of pydot-ng, @carlos-jenkins of pydot-plus, and @ajsteven130, whose fork has recent work.

@ajsteven130
Copy link

Hello,

For my fork, I just went through and cleared all the errors to get pydot to install on Python 3.4. It installs and works fine, but I am not sure it should be counted on as an official package. I'd be very happy if the small of work there is useful and could be integrated into a better maintained repository.

If there is any way I can help, let me know

@johnyf
Copy link

johnyf commented Nov 16, 2015

bmcorser has a PyPI entry for Python 3 called pydot3k. Note that it installs as pydot, so changes needed in source code. This enables conditional dependency selection, until the pydot entry is updated.

@prmtl
Copy link

prmtl commented Nov 18, 2015

Our fork (pydot-ng) was created because we needed the work from https://github.com/nlhepler/pydot and a package on PyPI (with support for Python 2.6). There are no much changes from original fork, mostly cleaning code/

@takluyver
Copy link

Just a reminder, it would be great if someone could work out which of the various forks is the best starting point, contact Ero to get the name on PyPI and upload a new release. I just helped another person on StackOverflow who was trying to use the original 'pydot' package on Python 3.

@johnyf
Copy link

johnyf commented May 9, 2016

I emailed @erocarrera (last week) about maintenance of pydot and its PyPI entry. I received no reply, thus I will evaluate the other packages (non-pydot) and switch to a maintained one.

The collection of pydot forks have various names and fixes, but are isolated side-projects that tend to become unmaintained projects too. For example, pydotplus is restructured (from a module to a package with a non-standard directory tree), and doesn't define any pydotplus.__version__ (__version__ was originally defined inside the standalone module pydot.py), but in pydotplus.version.

PEP 8 is not followed, and top-down parsing (pyparsing) doesn't scale to what bottom-up parsing can do (lex-yacc, i.e., ply and other parser generators). This seems to suggest using a newer and maintained package, for example graphviz (even if it doesn't have a parser, after all serves mostly as a backend).

For posterity, carlos-jenkins/pydotplus#1.

@nlhepler
Copy link
Owner

nlhepler commented May 9, 2016

Hey all,

I think moving to a maintained version of pydot is definitely the way to go. I modified this package to assist me in my graduate studies, but I'm afraid I don't have the bandwidth to maintain it. Either pydot-ng or pydotplus seems to be the way to go.

TL;DR: I don't have the bandwidth to maintain this package, please look at forks, including pydot-ng and pydotplus.

@johnyf
Copy link

johnyf commented May 9, 2016

@erocarrera has added me as a maintainer for pydot (on GitHub and PyPI), so we can start updating the master branch, and make a release. I think that this addresses the OP.

@takluyver
Copy link

Excellent, thanks @johnyf

@johnyf
Copy link

johnyf commented Nov 10, 2016

pydot is being maintained, and the latest version available on PyPI. I would suggest closing this issue.

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

No branches or pull requests

7 participants