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.

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

Maintainers Wanted #17

Open
gtalarico opened this issue Jun 5, 2019 · 13 comments
Open

Maintainers Wanted #17

gtalarico opened this issue Jun 5, 2019 · 13 comments

Comments

@gtalarico
Copy link
Owner

I am spread too thin with other OS projects, and since I don't use this project it's hard to justify spending time in this vs others.
I am happy to stay involved in the issues and help where I can,
but won't be able to continue development on this at this time.
Let me know if you are interested in helping maintaininig and developing it.
I would be happy to offer guidance.

@mostaphaRoudsari
Copy link

We should be able to help with Rhino/ Grasshopper related stubs. Specially if there is a way to automate the process and then it will be a matter of running the script every couple of months.

@gtalarico
Copy link
Owner Author

It would be nice if stub gen happened in CI, so someone could just PR a new Assembly
and it would rebuild and deployed to release.

@mostaphaRoudsari
Copy link

I'm pretty sure that can be set with some help from @AntoineDao!

@AntoineDao
Copy link

Oh hi! I like CI/CD 😄 We can set you up through a PR if you can let me know which python versions this is meant to run against (be tested on) as well as how you are currently releasing/distributing your code.

@gtalarico
Copy link
Owner Author

gtalarico commented Jun 5, 2019 via email

@AntoineDao
Copy link

Conveniently I've been playing with Azure Pipelines lately and they natively support windows VMs for CI/CD. How is this project currently distributed/installed? Is it on pypi? Is it a git download of the repo? Download of a binary?

@gtalarico
Copy link
Owner Author

These are stubs for editors auto complete so there is not a clear or consitent deployment strategy.

Currently docs recommend downloading repo and pointing your editor's python completion path to the stubs folder within the repo.

Maybe built stubs should be packaged into a release without the source code and users would download only that.

@AntoineDao
Copy link

Which editors does it currently work for? (ie: I mainly use vscode but I've got a feeling you're use case for this is within GH or Dynamo editors right?)

@mostaphaRoudsari
Copy link

These are stubs for editors auto complete so there is not a clear or consitent deployment strategy.

I think the main question for now is how do you generate them? I see in README that it is generated using a PyCharm module. Can we run that from the command line? and if yes how should one do that?

@gtalarico
Copy link
Owner Author

@AntoineDao checkout readme and wiki for editor docs
https://github.com/gtalarico/ironpython-stubs/wiki

@mostaphaRoudsari pycharm generator module is vendored in this repo.
Stubs are generated from cli but the cli interface is a bit cumbersome and incomplete.
See issue #10 and readme for details on cli is used

@PavelAltynnikov
Copy link

Hi everyone, who is the main developer of this project now?

@galaplexus
Copy link

Can we open permissions to create branches and do PR on the project?
Would like to contribute at least some documentation.

@gtalarico
Copy link
Owner Author

Hi @PavelAltynnikov @galaplexus anyone can submit a pull request.
PRs don't have to be from branches in this repo, they can be submitted from forks.

That said, unfortunately I am no longer able to maintain this project, so I am happy to add anyone here as a maintain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants