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
There are a few things in the README file which may confuse potential users. Below is an (incomplete) list of things that need considering. I will submit a new PR to cover some of the easy points.
Some links are out of date (pointing to my old repo, which has now been renamed) (see PR Update README #9)
The version number hasn't been updated since this fork started. It would be good to have a new version number to identify library versions based on this repo.
PyPI links to an old version (kevinpt's). This is confusing because when users run pip install hdlparse they won't get the version from this repo.
For the last point we could try a few solutions:
We could try to get in touch with kevinpt to see if we can get the PyPI hdlparse package to point to this repo
If we cannot reach kevinpt, perhaps PyPI could transfer ownership?
We could bump the version to 2.0.0, then make a new hdlparse2 package on PyPI?
We could use a different name altogether for a new PyPI package?
Looking forward to hearing your thoughts on this topic.
Cheers,
Wouter
The text was updated successfully, but these errors were encountered:
There are a few things in the README file which may confuse potential users. Below is an (incomplete) list of things that need considering. I will submit a new PR to cover some of the easy points.
pip install hdlparse
they won't get the version from this repo.For the last point we could try a few solutions:
Looking forward to hearing your thoughts on this topic.
Cheers,
Wouter
The text was updated successfully, but these errors were encountered: