-
Notifications
You must be signed in to change notification settings - Fork 7
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
Standardize on example URLs across package documentation #171
Comments
I would strongly support Regarding URLs I would slightly prefer something that's unlikely to accidentally work, |
Something to consider with |
This is true, whilst we are stuck with As you say the easy fix for windows is that package, there isn't an equivalent for *nix systems, since the location will vary depending on how you have openSSL, and whether you've built it yourself or are using a packaged version. This is not a problem that has an easy solution, see discussions here and here for some context. In the interrim I think as long as we make it clear for each package how custom certificates may be loaded, we shouldn't overly inconvenience users. If a user decides to connect to an insecure |
Hi @Andy-Grigg @da1910 - as you may already know, this repository is starting to serve the purpose of a "metapackage" (i.e. containing the different PyAnsys packages compatible with a certain Ansys version (221, 222, 231...). I am doing some cleanup on the repo and just came across this issue. I have some questions:
I will be closing automatically the issue if by August 26th I do not get a response. Thanks in advance! |
Hi @RobPasMue . Happy to close this. It was as you said in your first bullet point, just trying to ensure that we think about a consistent approach to referring to example servers when it comes to documentation. I think it's still an issue that we should aim to reach a consensus on, but I'm happy for it to be closed if needed. |
Yes, I think it is outside the scope of this repository from now onwards. But it is definitely something to take into account. I am transferring it to the dev-guide repository, in which we are providing guidelines for all PyAnsys repositories! I think it is the most appropriate location at this point =) |
Most of the packages within PyAnsys refer to remote resources using URLs. We should standardize how we refer to example server locations in docs:
The text was updated successfully, but these errors were encountered: