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

Create instructions for Git + Python on Windows #6

Open
aaaaalbert opened this issue May 4, 2016 · 5 comments
Open

Create instructions for Git + Python on Windows #6

aaaaalbert opened this issue May 4, 2016 · 5 comments

Comments

@aaaaalbert
Copy link
Contributor

Our buildscripts require Python and Git to work together. Setting up these on Windows can be tricky, especially regarding how / where Python is added to the $PATH environment variable, is / isn't installed for all users, and so on.

We should perhaps find one or two simple, standardized use cases that we document in a step-by-step tutorial.

aaaaalbert added a commit that referenced this issue Jul 4, 2017
We have been supporting 1.8 ever since PR #21 fixed issue #6. This commit now fixes the docs too.
@aaaaalbert
Copy link
Contributor Author

@wecsam, given your Windows shell skills, do you want to take a stab at this issue?

@wecsam
Copy link
Contributor

wecsam commented Nov 1, 2017

@aaaaalbert Sure, I'll take a look. Where are the existing buildscripts?

@aaaaalbert
Copy link
Contributor Author

Cool! The build scripts are here, https://github.com/SeattleTestbed/buildscripts/ . The build instructions are here, https://github.com/SeattleTestbed/docs/blob/master/Contributing/BuildInstructions.md .

There are three issues as far as I can see:

  • Python on Windows needs some extra care so that it sets up all PATHs correctly and can be started from the command line. Otherwise, we cannot run Repy.
  • Python must also run from within git-bash (which seems to be the most popular way to have a Git CLI on Windows). Otherwise it's a pain to check out all dependencies and build Seattle components for later use (e.g. repy_v2 and seash).
  • Related to this, the build scripts must be able to call git. On Unixoid systems, we use Popen, but again there seem to be path issues on Windows.

So we will need Windows-aware installation instructions that make the components work together, and perhaps modifications to the buildscripts too.

@wecsam
Copy link
Contributor

wecsam commented Nov 16, 2017

Unlike writing a command to loop through some files, that's not something that I'll be able to do in two minutes. I'll revisit this after final exams.

@aaaaalbert
Copy link
Contributor Author

Thank you, much appreciated!

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

No branches or pull requests

2 participants