-
Notifications
You must be signed in to change notification settings - Fork 56
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
Release tag that supports Python 3 #67
Comments
Hi! Actually the repo is somewhat a mess. That's my fault, I have no time to keep it tidy and updated. The develop branch is not very active and the python3-support one is dead. Currently most of PR go to the master branch, which supports Python3, PyTables3 PyQt5 and QtPy so your package should be based on master. At the moment I'm fixing bugs as fast as I can. I suspect/know that there are a few serious/annoying bugs and I'd like to fix them before releasing v2.2 but I don't have a timeline for the release :-( Sorry for not being more helpful. |
Hi @uvemas, why don't release a beta to pypi? |
Hi, $ twine.exe upload dist/* It seems there is a conflict with the existing ViTables package, and my package. Ast he first packager registered the package before than me then I cannot upload packages with the same name. I'm trying to contact the packager in order to fix the problem. |
Thanks @uvemas! I have a recipe for conda-forge submitted at conda-forge/stage-recipes#3052. If anyone wants to be a maintainer, please let me know! Also, I am happy to close this, or if you want to wait for the pypi issue to be resolved, that is OK too. |
Hi @scopatz. I don't know conda but Francesc Alted told me a few days ago that it is really nice and is the favorite packaging system among scientists so I'll have a look to it when I have some spare time (maybe next year :-) |
Haha! |
Hello! I am trying to put together a conda-forge package for vitables. Right now I am running into the issue that v2.1 only support Python 2. However, it seems like develop should support Python 3. Is there an expected timeline on when a v2.2 will be tagged? Thanks!
The text was updated successfully, but these errors were encountered: