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

updated pyflyte documentation #2877

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

sumana-2705
Copy link

Tracking issue: #5435

Why are the changes needed?

These modifications aim to enhance the initial user experience by providing clearer documentation for the Pyflyte package.

What changes were proposed in this pull request?

  • added example usage of --source in help message
  • included a structure in help message for better understanding of the usage of --pkgs option

Check all the applicable boxes

  • I updated the documentation accordingly.
  • All new and existing tests passed.
  • All commits are signed-off.

Signed-off-by: sumana sree <sumanasree2705@gmail.com>
Signed-off-by: sumana sree <sumanasree2705@gmail.com>
…p string

Signed-off-by: sumana sree <sumanasree2705@gmail.com>
Signed-off-by: sumana sree <sumanasree2705@gmail.com>
@sumana-2705
Copy link
Author

Hello @fg91 @davidmirror-ops

I accidentally committed changes without signing off in my last pull request. I have updated the files based on your feedback. Could you please review it again and let me know if any other changes are needed.

@fg91
Copy link
Member

fg91 commented Oct 31, 2024

Hello @fg91 @davidmirror-ops

I accidentally committed changes without signing off in my last pull request. I have updated the files based on your feedback. Could you please review it again and let me know if any other changes are needed.

When clicking on the failed CDO CI stage, there will be a hint how you can re-sign a commit and force push so that you don't have to open an new PR, just for the future ...

@@ -40,7 +40,7 @@
required=False,
type=click.Path(exists=True, file_okay=False, readable=True, resolve_path=True, allow_dash=True),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you have a minimal working example that shows how the --source argument of pyflyte package is supposed to be used? I'm asking because I ever only use the --pkgs arg and I don't know in which situation it makes sense to use the --source arg. I feel as part of this issue the difference should become clear from the help messages.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fg91 I have no idea about working example, will this help message works?

help="Local filesystem path to the root of the package. Use --source when specifying the root directory of your workflows. Example: --source /path/to/workflows. Use --pkgs to specify package names directly.",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's useful but will let @fg91 comment on this one

Copy link
Member

@fg91 fg91 Nov 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I unfortunately also don't have an idea how the --source tag is supposed to be used over the --pkgs arg.

My proposition would be to merge this PR as is (after this tiny nit has been merged) but to leave the issue open and then ask in Flyte's ask-the-community channel whether anyone knows. If yes, we can make a second PR explaining the diff. If there isn't any real use for the --source arg, we can create an issue to deprecate it.
What do you think about this?

Signed-off-by: sumana sree <sumanasree2705@gmail.com>
Signed-off-by: sumana sree <sumanasree2705@gmail.com>
sumana-2705 and others added 3 commits November 15, 2024 15:40
Signed-off-by: sumana sree <sumanasree2705@gmail.com>
Signed-off-by: sumana sree <sumanasree2705@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants