/proc/4/root/var/lang/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/generator
This explorer reads the filesystem of the server it runs on, so /workspace/user isn't present here. Browsing and the terminal still work against this server's own disk from /.
# Copyright (c) 2011 Google Inc. All rights reserved.# Use of this source code is governed by a BSD-style license that can be# found in the LICENSE file. """gypsh output module gypsh is a GYP shell. It's not really a generator per se. All it does isfire up an interactive Python session with a few local variables set to thevariables passed to the generator. Like gypd, it's intended as a debuggingaid, to facilitate the exploration of .gyp structures after being processedby the input module. The expected usage is "gyp -f gypsh -D OS=desired_os".""" import codeimport sys # All of this stuff about generator variables was lovingly ripped from gypd.py.# That module has a much better description of what's going on and why._generator_identity_variables = [ "EXECUTABLE_PREFIX", "EXECUTABLE_SUFFIX", "INTERMEDIATE_DIR", "PRODUCT_DIR", "RULE_INPUT_ROOT", "RULE_INPUT_DIRNAME", "RULE_INPUT_EXT", "RULE_INPUT_NAME", "RULE_INPUT_PATH", "SHARED_INTERMEDIATE_DIR",] generator_default_variables = {} for v in _generator_identity_variables: generator_default_variables[v] = "<(%s)" % v def GenerateOutput(target_list, target_dicts, data, params): locals = { "target_list": target_list, "target_dicts": target_dicts, "data": data, } # Use a banner that looks like the stock Python one and like what # code.interact uses by default, but tack on something to indicate what # locals are available, and identify gypsh. banner = ( f"Python {sys.version} on {sys.platform}\nlocals.keys() = " f"{sorted(locals.keys())!r}\ngypsh" ) code.interact(banner, local=locals)