Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Josh Black
    @joshblack
    Unfortunately, the Windows error is totally known and is possibly related to that mac error in the sense that the patterns aren't working
    I'm curious if it's a shell thing now given that our patterns are things like scss/*.scss
    Also, sorry this has been such a headache setting this up!
    DAK
    @dakahn
    Well they're Windows by way of WSL running Ubuntu -- which is what I just successfully built with
    Josh Black
    @joshblack
    This has become such a thing 😭
    Kimberly Andersson
    @kimberlyandersson
    it's an awesome third day for my newest intern haha
    DAK
    @dakahn
    I have that right, right @kimberlyandersson?
    Josh Black
    @joshblack
    Ugh, I bet. On the Mac side, are they using the stock Terminal.app ?
    Kimberly Andersson
    @kimberlyandersson
    @dakahn - what directory did you clone the project into?
    Josh Black
    @joshblack
    We recently had an intern join who went through setting things up, but I think she is using iTerm.
    Kimberly Andersson
    @kimberlyandersson
    yep. (it's only me on mac)
    Josh Black
    @joshblack
    Perfect 👌 Let me play around with that then and see what's going on. DA has the WSL support covered I think 🙂
    DAK
    @dakahn
    I cloned into a directory on my Windows OS. Specifically a folder called projects.
    Then from a terminal for WSL Ubuntu I cd into that folder and run the subsequent commands
    Kimberly Andersson
    @kimberlyandersson
    like through /mnt/c/...?
    DAK
    @dakahn
    Exactly!
    if I type pwd in my terminal the output for my root is /mnt/c/Users/{username}
    This is weird, I know. The section in this article called "FAQ: Where do my project files live?" explains this relationship really well
    hshockley
    @hshockley
    Hey @dakahn, installing in /mnt/c/Users/.../Desktop gives me an error that node-gyp can't find the python executable on my path, even though it is on my path through checking echo $PATH and windows env variables
    Whats the output of echo $PATH for you?
    DAK
    @dakahn
    Are you using Node for Windows? Or Node installed in WSL Ubuntu (or the like)
    hshockley
    @hshockley
    Node installed in WSL Ubuntu
    10.15
    DAK
    @dakahn
    In my root
    /home/{username}/.nvm/versions/node/v10.16.0/bin
    among a host of other things
    hshockley
    @hshockley
    10.15.3 which is the one I am currently using through nvm and 10.16
    DAK
    @dakahn
    Either v10 should be okay, can you post your terminal output -- specifically that python error you talked about before?
    DAK
    @dakahn
    also -- what's the output of running python -V
    (capital V)
    hshockley
    @hshockley
    Python 2.7.15rc1
    DAK
    @dakahn
    okay, can you show me the terminal output when you try and run -- the python error
    hshockley
    @hshockley
    2019-07-10 17_36_59-hshockley@wal-l-hs02_ _mnt_c_Users_hshockley_Desktop_RocketCarbon2_test_carbon.png
    2019-07-10 17_37_32-hshockley@wal-l-hs02_ _mnt_c_Users_hshockley_Desktop_RocketCarbon2_test_carbon.png
    DAK
    @dakahn
    Did you install python for WSL?
    it looks like it's trying to run a Windows executable, but you'd need to have Python3 installed in your dev environment (WSL)
    sudo apt install python3
    echo "alias python='python3'" >> ~/.bashrc
    source ~/.bashrc
    my output in WSL for python -V is Python 3.6.8
    DAK
    @dakahn
    @hshockley how'd installing python3 go?
    hshockley
    @hshockley
    Followed the steps but not luck. python -V gives version 3.6.7 and I checked .profiles to make sure the alias was there. Tried uninstalling python2.7 but that didn't seem to help at all
    DAK
    @dakahn
    @hshockley doing some research on your problem and I came across this:
    looks like those python executables are placeholders meant to prompt a Windows user to install Python3 in the Windows store, but are being hit via WSL as your python installation and so erroring out. I haven't encountered this problem myself. :confused:
    DAK
    @dakahn
    more still, it looks like existing Windows path variables are imported to your WSL install by default
    DAK
    @dakahn

    Okay, so it looks like there are two solutions to your problem @hshockley depending on your version of Insider Build:

    Either of those solutions should let you access the correct install of Python3 on your WSL environment

    DAK
    @dakahn
    Ah, also one more point -- you're definitely going to need a version of Python 2 alongside Python 3 -- lots of software requires it