-
Notifications
You must be signed in to change notification settings - Fork 88
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
providing up-to-date Pypi package #212
Comments
Hi there, first of all, I would like to salute @betodealmeida, @laliberte, @jameshiebert, @tomkralidis and all other contributors for conceiving and maintaining this excellent software package. After coming here through earthobservations/wetterdienst#287 (comment) as suggested by @mhaberler, we found the package to be a little bit unmaintained. However, thanks to different fixes and suggestions by community members (thanks @jerabaul29, @jblarsen, @MBARIMike and @mhaberler) on behalf of #167, #197 and #217, we have been able to successfully install, run and operate a DAP server and the respective client, both based on Pydap. In this manner, we wanted to take the chance to contribute the canonical installation command which will make things work. We hope it will be useful for others until an updated package will be available from PyPI.
With kind regards, |
Hi there, I want to support the request of a new pypi package. We currently develop a tool for a broader community, where we rely on the solution of #154 which has been merged in October 2018. The dependency to this package could be mentioned in the
but we would much rather prefer to be more general and reference it by e.g. This is a great package and more and more scientific data is available through OPeNDAP and users accessing it might rely on this package. Are you planning to make a new release? I'm happy to help where I can. All the best, |
Even if a release to PyPi is not feasible at the moment could we have a new pinging @tomkralidis since he is the one that merged the latest Pull Requests |
Thanks for the report @pmav99 et al. We will be cutting a new release shortly. |
A new release has been dropped. I need to submit it to PyPi next... |
Any updates on the PyPi package? For the record, we want to release a package that depends on pydap 3.3.0 and we can't do so because when we try to upload our package, PyPi rejects it with:
This is a known issue that has been resolved as "won't fix". Further info: pypi/warehouse#9404 |
@captainkirk99 any update on PyPI publishing? |
Just a reminder, if you find the time to pubilsh on PyPI, it would be really great :) |
the most resent version on PyPI is from 2017 - are there any reasons not to publish 3.3.0 to PyPI? |
@captainkirk99 any update on PyPI publishing? |
Don't want to be a pest, but a PyPI release would be great! :) Since @captainkirk99 is not responding (I really hope everything is fine..) I am pinging the other maintainers of the pydap package on PyPI hoping that they still have access: @shoyer @betodealmeida @jameshiebert |
Now that v3.4.0 and v3.4.1 are on PyPI, I think this issue can be closed :) |
Closing this issue as this has been addressed by a new PyPI release last year. Thank you everybody 🚀 |
It looks like the last PyDap release was in 2017 from the information on this page:
https://pypi.org/project/Pydap/#history
The package installed through pip is therefore quite outdated. For example, using pydap obtained from a pip install, this issue:
#162
is present, while using pydap installed from a git clone and local install, the issue is solved...
Therefore, would it be possible for the maintainer / owner of pydap here / on Pypi to push the up-to-date code to Pypi? :)
The text was updated successfully, but these errors were encountered: