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

Describe in readme programming languages supported. #245

Closed
pacospace opened this issue Mar 29, 2021 · 3 comments · Fixed by #341
Closed

Describe in readme programming languages supported. #245

pacospace opened this issue Mar 29, 2021 · 3 comments · Fixed by #341
Assignees
@pacospace
Labels
area/documentation Issues or PRs related to documentation, tutorials, examples, ... kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.

Comments

@pacospace
Copy link
Contributor

Is your feature request related to a problem? Please describe.
As Data Scientist using JupyterLab notebook,

I can use kernels with different programming languages. Currently jupyterlab-requirements support only Python ecosystem.

Describe the solution you'd like
Add section into README with a table showing programming language and dependency resolver available for jupyterlab-requirements.

Describe alternatives you've considered

Additional context
Related-To: #244
@pacospace pacospace added area/documentation Issues or PRs related to documentation, tutorials, examples, ... sig/docs sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. kind/documentation Categorizes issue or PR as related to documentation. labels Mar 29, 2021
@goern
Copy link
Member

goern commented Jun 10, 2021

/priority important-soon

@sesheta sesheta added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 10, 2021
@sesheta
Copy link
Member

sesheta commented Jul 15, 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 the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 15, 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 Jul 16, 2021
@pacospace pacospace mentioned this issue Jul 16, 2021
Merged
2 tasks
@pacospace pacospace self-assigned this Sep 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pacospace pacospace

Labels
area/documentation Issues or PRs related to documentation, tutorials, examples, ... kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Introduce Horus: jupyterlab requirements CLI pacospace/jupyterlab-requirements
3 participants
@goern @pacospace @sesheta