Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix argcomplete for conda build #521

Closed
asmeurer opened this issue Jan 22, 2014 · 5 comments
Closed

Fix argcomplete for conda build #521

asmeurer opened this issue Jan 22, 2014 · 5 comments
Assignees
@asmeurer
Labels
locked [bot] locked due to inactivity type::bug describes erroneous operation, use severity::* to classify the type

Comments

@asmeurer
Copy link
Contributor

No description provided.

@ghost ghost assigned asmeurer Jan 22, 2014
@ilanschnell
Copy link
Contributor

How is this supposed to work, now that conda build calls the external conda-build?

@asmeurer
Copy link
Contributor Author

I haven't looked at it yet, but it should be doable. Argcomplete has some APIs.

@ilanschnell
Copy link
Contributor

Anyway, I wouldn't call it a bug, just a "nice to have feature".

@asmeurer
Copy link
Contributor Author

It's a bug insomuch as it's a regression. Also it drives me nuts, which is why I will eventually implement it...

@github-actions
Copy link

Hi there, thank you for your contribution to Conda!

This issue has been automatically locked since it has not had recent activity after it was closed.

Please open a new issue if needed.

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Oct 10, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@asmeurer asmeurer

Labels
locked [bot] locked due to inactivity type::bug describes erroneous operation, use severity::* to classify the type
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@asmeurer @ilanschnell @kalefranz