-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add build
subcommand for building project
#1
Conversation
<natures> | ||
<nature>org.python.pydev.pythonNature</nature> | ||
</natures> | ||
</projectDescription> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll let adding these slide. :]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
build_type_choices
probably belongs in api
and should become an enumeration now that it can be selected by something other than CLI text.
github.com/epcpower/ccstudiodss/commit/0641a7d5924b5ba1686f6b7f70ec881b1b6e998d |
Sorry, I see the click link now. Here's the basic conversion but I'll gander through the link for something niftier. Maybe an actual click type. build_type_strings = [build_type.name for build_type in Build types]
build_type = BuildTypes[chosen_string] |
Yeah, no named tuple. Stdlib Enum or enum34 from PyPI. Either PR for Click similar to the last suggestion in the ticket or something like I have above. I haven't contributed to click so I don't know how the process goes with them. |
Note that GitHub inserts the commits into the history here so no need to link them. |
Move build functionality from grid-tied.