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

Instruction regarding development on Windows #103

Merged
merged 1 commit into from
Jan 28, 2022

Conversation

jgd10
Copy link
Contributor

@jgd10 jgd10 commented Jan 26, 2022

Added instruction on how to develop the package on Windows as opposed to
Linux, with notes that I would have needed when I tried to do it.

This should help users in the long run because whilst the package is
set to be depreciated in the future development is still required
because of how closely it is tied to pymapdl.

Should the bit I've added be reworded and also maybe moved to the CONTRIBUTING.md file? I would appreciate a quick proofread! I think it would be worthwhile to include a message like this somewhere but I'm not sure as to the best place it should go.

Added instruction on how to develop the package on Windows as opposed to
Linux, with notes that I would have needed when I tried to do it.

This should help users in the long run because whilst the package is
set to be depreciated in the future development is still required
because of how closely it is tied to pymapdl.
Copy link
Collaborator

@akaszynski akaszynski left a comment

Choose a reason for hiding this comment

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

Thanks, we needed that. Should have support up to 3.10 as the build works on windows, but we can get the docs for that later.

@akaszynski akaszynski merged commit 2300f8d into main Jan 28, 2022
@akaszynski akaszynski deleted the feat/windows_development_guide branch January 28, 2022 17:42
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.

2 participants