Planting the seeds for a vospace module#528
Draft
andamian wants to merge 2 commits into
Draft
Conversation
Contributor
|
I am *totally* in favour of having VOSpace support in pyVO. Since
I've never actually done any work with VOSpace, I can't say much on
implementation and API, though.
But this would be a very nice opportunity to finally get VOSpace
registration done properly. If I remember right, vos URIs are built
around ivoids, and thus to resolve them you'd have to engage the
Registry. Last time I looked, that's probably not what happens in
practice, as no (active) VOSpace services were actually registered.
So... I'd be more than happy to figure out this part of this
endeavour.
|
Contributor
Author
|
Yes, it should be able to resolve URIs of the form Our existing tool installs a number of CLI commands such as |
Contributor
|
On Thu, Feb 29, 2024 at 09:01:24PM +0000, Adrian wrote:
Our existing tool installs a number of CLI commands such as `vls`,
`vcm` etc (similar to their linux counterparts or to the `scp`
remote one). These tools are very popular with our users. Do you
see that as being outside the scope of `PyVO` which is just a
library?
I seem to remember astropy came with a few command line programs,
even if I now can't find them any more. Me, I'd be fairly relaxed
about providing some *entry points* to some modules.
If, on the other hand, significant amounts of argparse code were
necessary to do something useful, that'd be a signal to me that a
separate package would probably be a better fit.
|
Member
They are here: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I started with something very simple - read a node and read a container node and its entire content. There's a lot of functionality missing but initially I'm seeking comments general comments regarding the data representation as well as style and overall functionality. There's already a stand-alone
VOSpacePython client (https://github.com/opencadc/vostools/tree/master/vos). This implementation aims to re-use as much as possible the existingPyVOinfrastructure.Even if it's work in progress, I still welcome early feedback.