amoeba commented on issue #4593:
URL: https://github.com/apache/arrow-adbc/issues/4593#issuecomment-7051545665

   This isn't yet done and I'd like to figure out a next step, both for the 
retired PyPI packages and also crates.io and Conda Forge packages.
   
   After looking into this for a bit today, all I think we can do is mark the 
two PyPI packages as archived, as originally suggested by the OP. Editing the 
description or project metadata would require a new release which we can't do. 
One caveat around PyPI project archival is that the field is only rendered on 
the project web view and isn't yet exposed in any APIs so, for example, LLM 
agents aren't likely to discover it. I've reached out to the PyPI team to ask 
about this.
   
   (See https://pypi.org/project/mdvis/ versus `$ curl -s 
"https://pypi.org/pypi/mdvis/json"; | grep "archiv"`)
   
   For crates.io, as far as I can tell, all we can do is delete the crate which 
isn't a good option. All metadata appears to be driven from the release and we 
can't easily create a new release.
   For Conda Forge, releases are immutable, only feedstock repos can be 
modified or archived and we still need the ADBC feedstock repo.
   
   I have two questions for anyone really:
   
   1. Are there any concerns with archiving 
https://pypi.org/project/adbc-driver-bigquery/ and 
https://pypi.org/project/adbc-driver-snowflake/
   2. Is there anything more we could do I'm missing?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to