Fix round tripping (in python impl)

now you can send back a handle the client sent to you and it will work

Changelog

in libimportx:

• stop it from being version dependent
• complicated round tripping errors…
  in libimportx-python:
• version update thing
• increment version number
• complicated round tripping errors…
  in libimportx-js (new repo):
• Initialize the project
• Initial commit

Finish up the implementation by making a README (for the python impl) and uploading to PyPI

Now you can pip install libimportx

Changelog

In libimportx:

• Add the libimportx-python implementation
  In libimportx-python
• Add README and upload to PyPI

Implement importx() ImportxOpaque ImportxModule ImportxNamespace

yay! now it is essentially done. you can use it now

however its currently essentially useless since i did not implement it in any language other than python yet

Changelog

in libimportx-python

• Implement the importx function and all the classes

Made the exportx implementation in Python

i made the python implementation for exportx and also some tests for it

Changelog

in libimportx

• Loosen restrictions on handles
  in libimportx-python
• Implement exportx and the tests for it
• Initial commit

for pesky ft reviewers: the screenshot is technically “output” not “code”
for normal people the screenshot shows me testing the client:

• first the thing that is exporting send over the token, it is correct so i send +
• now i send a request to read the variable und which does not exist, so the client returns an error, errors are prefixed with minus
• then i read mydict which is successful so its prefixed with plus
• i try to read a file but files cant be sent over JSON so it uses this special syntax. i can still interact with the file using its methods
• i try to read a function similar story
• i call the function a few times, the function is supposed to return true then false then so on which it does
• i try to read the json module however modules cant be sent over JSON
• i try to read the function json.dumps
• i try to call json.dumps but i didnt put any args so it errors
• i made a mistake with the next one, i forgot to make the args an array so the client thought each char was an argument
• then i call it correctly (twice) and it works

Refine the protocol

yeah turns out the previous one had many errors and was unimplementable so i fixed than and made it better

• The JSON output always starts with + or - for success and error. This means I can read one byte to see if it is successful or not.

• Dynamically generated functions (like functions returning functions) could not be serialized before because they didn’t have an identifier as they were not in any variable. Now it allows both static and dynamic functions.

• Compiled languages and languages which dont use # for comments would straight up not work since without a shebang the OS would not be able to figure out how to run it. Now the library itself figures it out.

• Data that could nto be serialized (eg file objects) would not work, now it just uses a special opaque type. so objects that dont exist/cant be moved to the other language can be used as well. (so i could write to a file object through languages!)

Changelog

• Refine the protocol to be more reliable

here is a diagram i made to explain how the opaque object thing works.

Document the api

wait what im documenting it before making it?? yes you heard that right. the reason im doing this is for procastination so that i have a clear and consistent implementation plan. i will have to make this in a million languages so im making sure i dont have to improvise

Changelog

• idk make the documentation first ig
• Initial commit

here is this diagram i made to explain the protocol loosely