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

Provide way to create a common Pipfile/Pipfile.lock optimized by Thoth from different notebook requirements #6

Closed
pacospace opened this issue Nov 12, 2020 · 10 comments
Closed

Provide way to create a common Pipfile/Pipfile.lock optimized by Thoth from different notebook requirements #6

pacospace opened this issue Nov 12, 2020 · 10 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@pacospace
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Provide way to create a common Pipfile/Pipfile.lock optimized by Thoth from different notebook requirements directly from Jupyter Lab

Describe the solution you'd like

one button, might be in the menu under kernels tab (context for Thoth), that would look at all notebooks and create a merged Pipfile and Pipfile.lock.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
See: thoth-station/jupyter-nbrequirements#282 (comment)
@pacospace
Copy link
Contributor Author

Related-To: #17

@sesheta sesheta added kind/feature Categorizes issue or PR as related to a new feature. and removed enhancement labels Jan 28, 2021
@sesheta
Copy link
Member

sesheta commented Apr 28, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2021
@sesheta
Copy link
Member

sesheta commented May 28, 2021

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 28, 2021
@pacospace
Copy link
Contributor Author

/remove-lifecycle rotten

@sesheta sesheta removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 9, 2021
@goern
Copy link
Member

goern commented Jun 10, 2021

/priority backlog

@sesheta sesheta added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Jun 10, 2021
@pacospace
Copy link
Contributor Author

Related-To: #324

@sesheta
Copy link
Member

sesheta commented Aug 4, 2021

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta
Copy link
Member

sesheta commented Sep 3, 2021

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta sesheta closed this as completed Sep 3, 2021
@sesheta
Copy link
Member

sesheta commented Sep 3, 2021

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@pacospace
Copy link
Contributor Author

Replaced by: #17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@goern @pacospace @sesheta