Ref: https://github.com/wslutilities/wslu/blob/221e85457c01e92db675cc7b24a49dfcdfacc6a9/src/wslsys.sh#L52-L55

Ref: https://github.com/wslutilities/wslu/blob/221e85457c01e92db675cc7b24a49dfcdfacc6a9/src/wslsys.sh#L36-L41

Ref: https://github.com/wslutilities/wslu/blob/e3df3ccfad08ba6ab7c2bc22f9a135c8ba58c819/src/wslact.sh#L6-L35

Why looking for maintainers?

I am currently working in Canonical (as you might already know) to work on Ubuntu for WSL and Ubuntu for Hyper-V. With the works I have, while spending my free time on building wslu, I find myself unable to spare enough time for wslpy. Hence, I am looking for one or two maintainers to help to complete and improving this project.

What should I do?

Currently, wslpy is half baked if you look into the code. Here are the current TO-DOs:

• implement wslpy.system;
  • implement registry(input, key);
  • implement RegEnvVarList() using __regInfoFetch__(input, key);
  • implement regEnvVar(input) to get environment variables via Registry.
• reimplement wslpy.exec.

Here are the goals:

• implement the same features provided by wslvar, wslsys and wslupath from wslu;
• (Optional) implement features by wslusc and wslact from wslu;
• Build a documentation/wiki for the project.

What should I do to become a maintainer?

You should submit at least one PR to the project for fixing one of the issues in TO-DOs. Once it is reviewed and merged, I will add you to the maintainer list. I will be using IRC for communication (#wslu in Freenode.net). You will also get an email address ending with wslutiliti.es with your name.

This tries to implement the enhancement proposed by wslutilities/wslu#176, especially the icon finding part.

Are there plans format the function's comments with the same format+information as the ones in the triple quotes?

Originally posted by @HayashiEsme in 6facbfb

Yes, please do.

Originally posted by @patrick330602 in #13

With reference to a desire to format comments like so I tried to keep to the formatting of wrapping multi line comments with triple quotes as the case has been in the other functions but I ran into an interesting issue:

esme@Esme-Prestige14W:/mnt/c/Users/Esme/Developer/wslpy/wslpy$ python3 system.py
File "system.py", line 112
"""
^
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 663-664: truncated \UXXXXXXXX escape

This isn't a feature of Python I was familiar with so I'll add some context: Python understands triple quotes that follow the start of a function as docstrings (https://www.python.org/dev/peps/pep-0257/), and expect text within it to follow 'coding styles'. In this case with code like this:

"""
Given a valid registry path, retrieves the value of an entry in the registry.
Eg: registry("HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment","OS") returns "WINDOWS_NT"

MAY return string type TODO: Doees this make sense?

A valid registry path typically includes (this this and this) 
"""

The use of the double quotes and \s create issues and require escaping. The result is that documentation looks like this:

"""
Given a valid registry path, retrieves the value of an entry in the registry.
Eg: registry(\"HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Environment\\",\"OS\") returns \"WINDOWS_NT\"

MAY return string type TODO: Doees this make sense?

A valid registry path typically includes (this this and this)
"""

Shall we change it to #-tagged comments to avoid this issue? Is there another place you'd like the comments to be placed otherwise Patrick?

In using #-tagged it should be alright to expect that a developer can use their text editor to quickly add #s to the comments made with a shortcut like ctrl-/ in VScode

I thought it would be important to create this in the same style as the ones in repos before, but to create this detailing pre-requisites specific to WSLpy (This would mean: WSL installed, and commands to pull and install)

I'm thinking of writing the pull request for this fix. I'll update as I know more about my day today

Ref: https://github.com/wslutilities/wslu/blob/221e85457c01e92db675cc7b24a49dfcdfacc6a9/src/wslsys.sh#L59-L79

Ref: https://github.com/wslutilities/wslu/blob/221e85457c01e92db675cc7b24a49dfcdfacc6a9/src/wslsys.sh#L26-L34

Ref: https://github.com/wslutilities/wslu/blob/e3df3ccfad08ba6ab7c2bc22f9a135c8ba58c819/src/wslact.sh#L37-L90

Ref: https://github.com/wslutilities/wslu/blob/221e85457c01e92db675cc7b24a49dfcdfacc6a9/src/wslsys.sh#L7-L10

Ref: https://github.com/wslutilities/wslu/blob/221e85457c01e92db675cc7b24a49dfcdfacc6a9/src/wslsys.sh#L21-L24

Ref: https://github.com/wslutilities/wslu/blob/221e85457c01e92db675cc7b24a49dfcdfacc6a9/src/wslu-header#L240-L257

• implement wslpy.system;
  • implement registry(input, key);
  • implement RegEnvVarList() using regInfoFetch(input, key);
  • implement regEnvVar(input) to get environment variables via Registry.

Ref: https://github.com/wslutilities/wslu/blob/e3df3ccfad08ba6ab7c2bc22f9a135c8ba58c819/src/wslact.sh#L92-L108

Ref: https://github.com/wslutilities/wslu/blob/221e85457c01e92db675cc7b24a49dfcdfacc6a9/src/wslsys.sh#L16-L19

Ref: https://github.com/wslutilities/wslu/blob/e3df3ccfad08ba6ab7c2bc22f9a135c8ba58c819/src/wslsys.sh#L133-L136

Background Information:

• Windows Build: 22000
• WSL: Ubuntu 21.04
• WSL Version: [e.g. 1 store]
• Version: 0.0.13

Describe the bug
Error when importing wslpy

from .__core__.check import is_interop_enabled, is_wsl
ModuleNotFoundError: No module named 'wslpy.__core__

To Reproduce

pip install wslpy

import wslpy

Expected behavior

No error

Additional context

Workaround:
Manually add the __core__ folder to the site-packages/wslpy/
the wslpy.__core__ package could be added in the setup.py packages argument at this line

Reimplement reg.exe related command to use powershell

Ref: https://github.com/wslutilities/wslu/blob/221e85457c01e92db675cc7b24a49dfcdfacc6a9/src/wslsys.sh#L43-L50

Should be 'reg.exe' instead of 'powershell.exe'

wslpy/wslpy/system.py

Line 41 in 11d2bee

cmd = u"powershell.exe query \"HKLM\\Software\\Microsoft\\Windows NT\\CurrentVersion\" /v \""+key+u"\" 2>&1"

pathlib.Path.resolve doesn't verify the existence of the path - it just builds it based on your input and converts it to the OS-specific format. As a result, isWSL would always return True.

>>> from pathlib import Path
>>> p = Path('/proc/sys/fs/binfmt_misc/WSLInterop').resolve()
>>> p
WindowsPath('C:/proc/sys/fs/binfmt_misc/WSLInterop')
>>> p.exists()
False

Is it possible that your documentation given in README.md represents some older architecture?
None of your examples

wslpy.isWSL
wslpy.convert.reg_list()
wslpy.convert.from_reg(input)
wslpy.convert.to_path(input, toType = PathConvType.AUTO)
wslpy.winsys.build
wslpy.winsys.branch
wslpy.winsys.long_build
wslpy.winsys.CmdExec(command)
wslpy.winsys.PwShExec(command)
wslpy.winsys.PwShCrExec(command)

can work.

isWSL is a function, not an attribute. And neither convert nor winsys are imported into the module, so any of the lines above would just give module 'wslpy' has no attribute 'winsys' (or 'convert')

Would you mind updating either the documentation or your __init__.py to reflect your new module structure?

This little tool was what I had been looking for and it would be a shame if it became unusable for others. And I don't want to create a pull request as the changes need a decision best made by the author, I think (change the docs or __init__.py ?)

Ref: https://github.com/wslutilities/wslu/blob/221e85457c01e92db675cc7b24a49dfcdfacc6a9/src/wslu-header#L111-L146