Support for Python 3 #1337

cclauss · 2017-11-14T08:33:48Z

See ~~#1150~~, ~~#1335~~, ~~#1336~~, and ~~https://travis-ci.com/nodejs/node/builds/79706150~~ (~~nodejs/node#21942~~)

Node Version:
Platform:
Compiler:
Module:

Verbose output (from npm or node-gyp):

The text was updated successfully, but these errors were encountered:

richardlau · 2017-11-14T12:48:27Z

Historically the blocker to this has been the gyp dependency and normally changes should be upstreamed there unless we're planning on forking gyp in which case we would want our own gyp project so that we can share the changes with the main Node.js project.

cc @nodejs/gyp

mthacker801 · 2018-02-08T17:12:48Z

I cannot successfully install Angular on my mac. I keep getting gyp error and when I look at gyp-mac-tool it says:
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb which failed Error: not found: python2
gyp verb which failed at getNotFoundError (/Users/thackerfam/AngularProj/angular-cli/node_modules/which/which.js:13:12)

I have had python 3 installed forever and do not want python 2 as it can cause havoc to have both installed as they are not compatible with one another. If this is the reason for my inability to use Angular, what should I do?

cclauss · 2018-02-08T17:38:55Z

On your Mac, what happens when you do:

python2 --version
/usr/bin/python --version
/usr/bin/python2 --version
/usr/bin/python2.7 --version

I would highly recommend Homebrew as essential if you are doing real development on a Mac.

Brew allows you to easily install both Python 2 and Python3 with: brew install python python@2

cclauss · 2018-02-08T18:47:37Z

A few Python 2 issues on gyp:

$ python2 -m flake8 . --count --select=E901,E999,F821,F822,F823 --show-source --statistics

./gyptest.py:61:47: F821 undefined name 'opts'
    extra_path = [os.path.abspath(p) for p in opts.path]  # <-- 'opts' should be changed to 'args'
                                              ^
./pylib/gyp/generator/make.py:1637:50: F821 undefined name 'target'
      print "WARNING: no output for", self.type, target  # <-- 'target' should be changes to 'self.target'
                                                 ^

SatishMHiremath · 2018-02-17T17:55:29Z

I have faced and fixed this issue relates node-sass and python error.Try installing latest angular cli command with the steps below

Set the system variable path as well:
C:\Users\windowsusername\AppData\Roaming\npm

C:\Users\windowsusername\AppData\Roaming\npm\node_modules@angular\cli\bin;

C:\Program Files\nodejs;

Then start using angular cli command prompt using:
angular client project folder path>npm install -g @latest

angular client project folder path>npm install -g node-gyp

stanleyxu2005 · 2018-02-26T16:30:46Z

It's a bit embraced that the original gyp project relies on python 2, and after couple of years, the patch is getting too big so that no people is dare to review and merge it. Need to give the gyp community more feedback to move this forward.

AdamMajer · 2018-03-02T12:06:33Z

Is there any interest in this? Python 2 is starting to get removed from distributions at this point.

timoxley · 2018-03-03T09:59:36Z

Python 2 is starting to get removed from distributions at this point.

Correct e.g. brew is now installing/upgrading to Python 3 by default.

The following just worked for me as I already had a python2.7 executable installed via brew:

npm config set python python2.7

However, if you don't have a python2.7 executable, I suspect you can do something like:

brew install python@2
# follow the instructions printed after installing `python@2` to get python 2 on your PATH 
# e.g. echo 'export PATH="/usr/local/opt/python@2/bin:$PATH"' >> ~/.bashrc
npm config set python python2.7

NetOpWibby · 2018-03-24T21:53:42Z

Tim's method should go in the README. I use ZSH and there was a message mentioned Xcode when I installed Python 2 so my process was as follows:

xcode-select --install

brew install python@2
echo 'export PATH="/usr/local/opt/python@2/bin:$PATH"' >> ~/.zshrc
npm config set python python2.7

ioquatix · 2018-05-04T10:21:04Z

For some reason, npm config set python python2.7 stopped working for me. Even after setting it, I get the error that node-gyp is trying to run python 3.6

cclauss · 2018-05-04T10:27:32Z

What does python2.7 --version return on your machine?

ioquatix · 2018-05-04T10:28:15Z

> python2.7 --version
Python 2.7.14

ioquatix · 2018-05-04T10:33:34Z

Here is the full error

^_^ > apm install      
Installing modules ✗
> node-pty@0.7.4 install /Users/samuel/.atom/packages/script-runner/node_modules/node-pty
> node scripts/install.js

script-runner@3.0.0 /Users/samuel/.atom/packages/script-runner
├── etch@0.14.0 
├── resize-observer-polyfill@1.5.0 
├─┬ shell-environment@0.3.1 
│ └─┬ os-locale@2.1.0 
│   ├─┬ execa@0.7.0 
│   │ ├─┬ cross-spawn@5.1.0 
│   │ │ ├─┬ lru-cache@4.1.2 
│   │ │ │ ├── pseudomap@1.0.2 
│   │ │ │ └── yallist@2.1.2 
│   │ │ ├─┬ shebang-command@1.2.0 
│   │ │ │ └── shebang-regex@1.0.0 
│   │ │ └─┬ which@1.3.0 
│   │ │   └── isexe@2.0.0 
│   │ ├── get-stream@3.0.0 
│   │ ├─┬ npm-run-path@2.0.2 
│   │ │ └── path-key@2.0.1 
│   │ ├── p-finally@1.0.0 
│   │ ├── signal-exit@3.0.2 
│   │ └── strip-eof@1.0.0 
│   ├─┬ lcid@1.0.0 
│   │ └── invert-kv@1.0.0 
│   └─┬ mem@1.1.0 
│     └── mimic-fn@1.2.0 
├── shellwords@0.1.1 
├─┬ temp-write@3.4.0 
│ ├── graceful-fs@4.1.11 
│ ├── is-stream@1.1.0 
│ ├── make-dir@1.2.0 
│ ├── pify@3.0.0 
│ ├── temp-dir@1.0.0 
│ └── uuid@3.2.1 
└── xterm@3.3.0 


gyp ERR! configure error 
gyp ERR! stack Error: Python executable "/Applications/Atom.app/Contents/Resources/app/apm/bin/python-interceptor.sh" is v3.6.4, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack     at failPythonVersion (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/node-gyp/lib/configure.js:454:14)
gyp ERR! stack     at /Applications/Atom.app/Contents/Resources/app/apm/node_modules/node-gyp/lib/configure.js:443:9
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:197:7)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at maybeClose (internal/child_process.js:877:16)
gyp ERR! stack     at Socket.<anonymous> (internal/child_process.js:334:11)
gyp ERR! stack     at emitOne (events.js:96:13)
gyp ERR! stack     at Socket.emit (events.js:188:7)
gyp ERR! stack     at Pipe._handle.close [as _onclose] (net.js:498:12)
gyp ERR! System Darwin 17.5.0
gyp ERR! command "/Applications/Atom.app/Contents/Resources/app/apm/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/.bin/node-gyp" "rebuild"
gyp ERR! cwd /Users/samuel/.atom/packages/script-runner/node_modules/node-pty
gyp ERR! node -v v6.9.5
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 
npm ERR! Darwin 17.5.0
npm ERR! argv "/Applications/Atom.app/Contents/Resources/app/apm/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/Users/samuel/.atom/.apm/.apmrc" "--userconfig" "/Users/samuel/.atom/.apmrc" "install" "--runtime=electron" "--target=1.7.11" "--arch=x64"
npm ERR! node v6.9.5
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR! node-pty@0.7.4 install: `node scripts/install.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-pty@0.7.4 install script 'node scripts/install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-pty package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs node-pty
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls node-pty
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/samuel/.atom/packages/script-runner/npm-debug.log

Here is my config

 > apm config list
; cli configs
globalconfig = "/Users/samuel/.atom/.apm/.apmrc"
user-agent = "npm/3.10.10 node/v6.9.5 darwin x64"
userconfig = "/Users/samuel/.atom/.apmrc"

; environment configs
node-gyp = "/Applications/Atom.app/Contents/Resources/app/apm/bin/../node_modules/.bin/node-gyp"
python = "/Applications/Atom.app/Contents/Resources/app/apm/bin/python-interceptor.sh"

; userconfig /Users/samuel/.atom/.apmrc

; globalconfig /Users/samuel/.atom/.apm/.apmrc
cache = "/Users/samuel/.atom/.apm"
progress = false

; node bin location = /Applications/Atom.app/Contents/Resources/app/apm/bin/node
; cwd = /Users/samuel/.atom/packages/script-runner
; HOME = /Users/samuel/.atom/.node-gyp
; "npm config ls -l" to show all defaults.

^_^ > npm config list
; cli configs
user-agent = "npm/3.10.10 node/v8.10.0 darwin x64"

; userconfig /Users/samuel/.npmrc
init.author.email = "samuel.williams@oriontransfer.co.nz"
init.author.name = "Samuel Williams"
init.author.url = "http://www.codeotaku.com"
python = "python2.7"

; node bin location = /opt/local/bin/node
; cwd = /Users/samuel/.atom/packages/script-runner
; HOME = /Users/samuel
; "npm config ls -l" to show all defaults.

Hmm, I'm sure I also had apm config set python=python2.7. Maybe that's why it's not working.

ioquatix · 2018-05-04T10:35:39Z

That's odd, maybe it's a bug in apm.

> apm config set python python2.7
> apm config list                
; cli configs
globalconfig = "/Users/samuel/.atom/.apm/.apmrc"
user-agent = "npm/3.10.10 node/v6.9.5 darwin x64"
userconfig = "/Users/samuel/.atom/.apmrc"

; environment configs
node-gyp = "/Applications/Atom.app/Contents/Resources/app/apm/bin/../node_modules/.bin/node-gyp"
python = "/Applications/Atom.app/Contents/Resources/app/apm/bin/python-interceptor.sh"

; userconfig /Users/samuel/.atom/.apmrc

; globalconfig /Users/samuel/.atom/.apm/.apmrc
cache = "/Users/samuel/.atom/.apm"
progress = false

; node bin location = /Applications/Atom.app/Contents/Resources/app/apm/bin/node
; cwd = /Users/samuel/.atom/packages/script-runner
; HOME = /Users/samuel/.atom/.node-gyp
; "npm config ls -l" to show all defaults.

Even thought I set it, it's not changed in the config!?

raininja · 2018-05-07T19:43:08Z

@ioquatix what does "apm config get" show?

[raijin@ishtar][~]%apm config get
; cli configs
globalconfig = "/home/raijin/.atom/.apm/.apmrc"
user-agent = "npm/3.10.10 node/v6.9.5 linux x64"
userconfig = "/home/raijin/.atom/.apmrc"

; environment configs
node-gyp = "/usr/share/atom/resources/app/apm/bin/../node_modules/.bin/node-gyp"

; userconfig /home/raijin/.atom/.apmrc
python = "python2.7"

; globalconfig /home/raijin/.atom/.apm/.apmrc
cache = "/home/raijin/.atom/.apm"
progress = false

; node bin location = /usr/share/atom/resources/app/apm/bin/node
; cwd = /home/raijin
; HOME = /home/raijin/.atom/.node-gyp
; "npm config ls -l" to show all defaults.

ioquatix · 2018-05-07T23:56:55Z

koyoko% apm config get
; cli configs
globalconfig = "/home/samuel/.atom/.apm/.apmrc"
metrics-registry = "https://registry.npmjs.org/"
scope = ""
user-agent = "npm/6.0.0 node/v10.0.0 linux x64"
userconfig = "/home/samuel/.atom/.apmrc"

; environment configs
python = "/usr/lib/node_modules/atom-package-manager/bin/python-interceptor.sh"

; project config /home/samuel/.npmrc
strict-ssl = true

; globalconfig /home/samuel/.atom/.apm/.apmrc
cache = "/home/samuel/.atom/.apm"
progress = false

; node bin location = /usr/bin/node
; cwd = /home/samuel
; HOME = /home/samuel/.atom/.node-gyp
; "npm config ls -l" to show all defaults.

koyoko% apm config set python foo
koyoko% apm config get           
; cli configs
globalconfig = "/home/samuel/.atom/.apm/.apmrc"
metrics-registry = "https://registry.npmjs.org/"
scope = ""
user-agent = "npm/6.0.0 node/v10.0.0 linux x64"
userconfig = "/home/samuel/.atom/.apmrc"

; environment configs
python = "/usr/lib/node_modules/atom-package-manager/bin/python-interceptor.sh"

; project config /home/samuel/.npmrc
strict-ssl = true

; userconfig /home/samuel/.atom/.apmrc

; globalconfig /home/samuel/.atom/.apm/.apmrc
cache = "/home/samuel/.atom/.apm"
progress = false

; node bin location = /usr/bin/node
; cwd = /home/samuel
; HOME = /home/samuel/.atom/.node-gyp
; "npm config ls -l" to show all defaults.

brennon · 2018-05-09T23:54:15Z

It's one thing to retain support for Python 2 (though many projects are dropping it altogether). It's another thing entirely to _not _ support Python 3. Please consider this. Python 3 is a decade old, after all... 😄

ostrolucky · 2018-05-12T10:20:42Z

star this https://bugs.chromium.org/p/gyp/issues/detail?id=36 to help resolve this issue

raininja · 2018-05-12T20:23:12Z

starred, not sure why 10 years have passed and we are still dealing with this!

Croydon · 2018-05-13T00:19:33Z

GYP is dead. Google moved on to GN.

ioquatix · 2018-05-13T00:35:56Z

What is GN?

Croydon · 2018-05-13T00:36:57Z

https://chromium.googlesource.com/chromium/src/tools/gn/#what-is-gn

raininja · 2018-05-13T01:25:34Z

Yea but this thread https://groups.google.com/forum/#!topic/gyp-developer/U66xtisrYRM says it's just a matter of Dirk landing and reviewing the patch.

raininja · 2018-05-13T01:27:48Z

My question is this: why can't we just fork gyp and add the patch and go with that?

cclauss · 2018-05-13T03:01:27Z

There is no reason why not. That is the way of open source. If no maintainer steps forward with a cogent plan that fits your needs, you can always hit the fork button.

cclauss · 2018-05-13T03:20:44Z

Perhaps @refack can help to keep things progressing on this repo.

iMichka · 2019-04-24T18:01:09Z

a sense of the degree of difficulty required to **set up and maintain an _external

It is doable. The issue will be more about visibility. More than 4 million install events in a year through homebrew will mean that we need to communicate to all these people about the node removal from homebrew-core, and give instructions on how to tap the new node tap. All the install scripts from the whole industry will probably need an updated too. There will be no automatic redirection to an external tap.

I do not want to pollute this thread more with homebrew discussions though. We are not the only ones to ship node, so the issue is more global than this. Not sure this issue is the best place to discuss all this. We have not taken any decision right now, my initial message was more a gentle nudge to warn you that bigger changes may come :)

AdamMajer · 2019-04-25T08:07:28Z

We are not the only ones to ship node, so the issue is more global than this.

Indeed, it's much more global than this. There has been discussion on removing python2 from openSUSE Tumbleweed distribution at beginning of next year. For those that don't know, Tumbleweed is the rolling release distribution of openSUSE project.

https://lists.opensuse.org/opensuse-factory/2019-04/msg00229.html

on the bright fresh chilly morning of 2020-01-02 we are going to remove python2 package (that's python 2.7.* interpreter) from Factory.

mingrammer · 2019-06-05T08:36:36Z

Is this in progress?

cclauss · 2019-06-05T09:13:38Z

@mingrammer #1723 (comment) lists some current Python 3 incompatibilities if you have some time to work on this. We also created GYP3 nodejs/node#26620

MattIPv4 · 2019-07-06T21:22:24Z

Would it be possible to edit the opening post in this thread with a general summary of the situation with regards to the move to Python 3 due to the Python 2 EOL and drop from Brew/macOS/Linux distros? It'd be great if that could then be kept up to date so the average user can easily see an overview of the current situation and the plan going forward :)

cclauss · 2019-07-07T10:24:48Z

Closing this PR as GYP seems to be Python 3 compatible:

node/node-gyp Travis CI tests are run and pass on Linux, macOS. Help needed on Windows Travis CI tests are failing on Windows #1801
GYP3 https://github.com/refack/GYP is also of interest and supports Python 3
Chromium GYP is also making Python3 progress https://chromium.googlesource.com/external/gyp

If you find any Python 3 incompatibles in this code, please open an issue.

NOTE: nodejs/node is not yet compatible with Python 3 but an effort is ongoing there.

superern · 2019-08-03T03:41:32Z

Python 2 is starting to get removed from distributions at this point.

Correct e.g. brew is now installing/upgrading to Python 3 by default.

The following just worked for me as I already had a python2.7 executable installed via brew:
npm config set python python2.7
However, if you don't have a python2.7 executable, I suspect you can do something like:
brew install python@2
# follow the instructions printed after installing `python@2` to get python 2 on your PATH 
# e.g. echo 'export PATH="/usr/local/opt/python@2/bin:$PATH"' >> ~/.bashrc
npm config set python python2.7

Thanks! this resolves my issues

slim-hmidi · 2020-07-01T13:53:03Z

I'm using Node.js v 12.18.2 and Python v3.8.1 on windows 10 and when I tried to run npm install I got this error:

gyp ERR! configure error
gyp ERR! stack Error: Command failed: C:\Program Files (x86)\Python\Python\python.EXE -c import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack   File "<string>", line 1
gyp ERR! stack     import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack                       ^
gyp ERR! stack SyntaxError: invalid syntax
gyp ERR! stack
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:303:12)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
gyp ERR! System Windows_NT 10.0.17134
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\x199377\\AppData\\Local\\Programs\\Git\\react-whiteapp\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\Users\x199377\AppData\Local\Programs\Git\react-whiteapp\node_modules\node-sass
gyp ERR! node -v v12.18.2
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1

cclauss · 2020-07-01T14:05:46Z

gyp ERR! node-gyp -v v3.8.0

Please upgrade node-gyp to v7 https://github.com/nodejs/node-gyp/releases

richardlau · 2020-07-01T14:18:46Z

@slim-hmidi If you want to use Python 3 you'll have to take up with node-sass as they're still depending on node-gyp ^3.8.0: https://github.com/sass/node-sass/blob/e1fc1580c2e979113c95850b8ae5d83845063ca5/package.json#L67

node-gyp added Python 3 support in the 5.x and later releases.

slim-hmidi · 2020-07-01T14:56:48Z

@richardlau I installed python v2.7.16 but still the same problem.

richardlau · 2020-07-01T15:00:13Z

If you have the same problem it means that node-gyp is still trying to use Python 3. Maybe try setting the PYTHON environment variable to point to your installed Python 2?

slim-hmidi · 2020-07-01T15:05:30Z

I uninstalled python 3 and python 2.7.16 and I'm reinstalling python 2.7.16 again and I will try again.

slim-hmidi · 2020-07-01T15:11:21Z

@richardlau it works now. thanks

lalomartins mentioned this issue Jan 22, 2018

gyp can't find Python, despite Python running when you type "python" #1268

Closed

Arcanemagus mentioned this issue Mar 5, 2018

[wip] Improve ability to detect Python 2 during build atom/atom#16885

Closed

NetOpWibby mentioned this issue Mar 24, 2018

Support for Python 3 #193

Closed

robrobbins mentioned this issue Apr 27, 2018

node-gyp unhappy with Python versions computablelabs/computable.js#56

Closed

refack added Feature Request gyp upstream issue / floating patch labels Apr 24, 2019

MadLittleMods mentioned this issue May 7, 2019

Cannot install usb-detection (v4.1.0): Command Failed MadLittleMods/node-usb-detection#82

Closed

lvaccaro mentioned this issue Jun 10, 2019

Invalid syntax while trying to build js-wrappers ElementsProject/libwally-core#108

Closed

wadethestealth mentioned this issue Jul 1, 2019

Installation error on Windows: zeromq@5.1.0 install nteract/hydrogen#1689

Closed

deepak1556 mentioned this issue Jul 6, 2019

Migrate from GYP to GN microsoft/node-pty#330

Closed

cclauss closed this as completed Jul 7, 2019

cclauss mentioned this issue Jul 7, 2019

doc: Declare that node-gyp is Python 3 compatible #1811

Closed

4 tasks

bsrdjan mentioned this issue Jul 30, 2019

node-gyp Python 3 support SAP/node-rfc#72

Closed

Josverl mentioned this issue Nov 12, 2019

Python 2.7.16 installed already, installs 2.7.15 anyways felixrieseberg/windows-build-tools#191

Closed

cclauss assigned cclauss and unassigned refack Mar 8, 2020

srl295 mentioned this issue May 11, 2020

build fails on OSX 10.10 nodejs/node#32452

Closed

cclauss added the Node Sass --> Dart Sass https://github.com/sass/node-sass/issues/2952 label Jul 3, 2020

ghost mentioned this issue Oct 12, 2020

Build fails with Python 3 due to old node-gyp version requirement bitwarden/web#670

Closed

KonnorRogers mentioned this issue Feb 4, 2021

Bug: Node-Gyp cant find a python executable reviewdog/action-eslint#70

Closed

Support for Python 3 #1337

Support for Python 3 #1337

Comments

cclauss commented Nov 14, 2017 • edited Loading

richardlau commented Nov 14, 2017

mthacker801 commented Feb 8, 2018

cclauss commented Feb 8, 2018 • edited Loading

cclauss commented Feb 8, 2018

SatishMHiremath commented Feb 17, 2018

stanleyxu2005 commented Feb 26, 2018

AdamMajer commented Mar 2, 2018

timoxley commented Mar 3, 2018 • edited Loading

NetOpWibby commented Mar 24, 2018

ioquatix commented May 4, 2018

cclauss commented May 4, 2018

ioquatix commented May 4, 2018

ioquatix commented May 4, 2018

ioquatix commented May 4, 2018

raininja commented May 7, 2018

ioquatix commented May 7, 2018

brennon commented May 9, 2018

ostrolucky commented May 12, 2018

raininja commented May 12, 2018

Croydon commented May 13, 2018

ioquatix commented May 13, 2018

Croydon commented May 13, 2018

raininja commented May 13, 2018

raininja commented May 13, 2018

cclauss commented May 13, 2018

cclauss commented May 13, 2018

iMichka commented Apr 24, 2019

AdamMajer commented Apr 25, 2019

mingrammer commented Jun 5, 2019

cclauss commented Jun 5, 2019

MattIPv4 commented Jul 6, 2019

cclauss commented Jul 7, 2019 • edited Loading

superern commented Aug 3, 2019

slim-hmidi commented Jul 1, 2020 • edited Loading

cclauss commented Jul 1, 2020

richardlau commented Jul 1, 2020

slim-hmidi commented Jul 1, 2020

richardlau commented Jul 1, 2020

slim-hmidi commented Jul 1, 2020

slim-hmidi commented Jul 1, 2020

cclauss commented Nov 14, 2017 •

edited

Loading

cclauss commented Feb 8, 2018 •

edited

Loading

timoxley commented Mar 3, 2018 •

edited

Loading

cclauss commented Jul 7, 2019 •

edited

Loading

slim-hmidi commented Jul 1, 2020 •

edited

Loading