-
Notifications
You must be signed in to change notification settings - Fork 4
a new mirror for testing #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Actually, I was able to test the new ffi providers i created by altering my local copy of the mirror located in the
Ok thanks will do! |
Just throwing ideas around here - You might make a dedicated command for adding mirrors locally, And another for resetting the mirror back to the officially downloaded one: Not that this has to happen in the |
Hi, just passed the deadline. Your idea is very close to what in my blueprint, I totally agree with your design. The reason why we might not immediately implement this is, we shall consider working better with spago. |
Ohh gotcha, that makes sense. I guess we should be waiting on that before making a decision on how to handle this issue |
It depends. If people including you and me feel very annoying about it, we can just implement what you want. |
@vanceism7 things got pushed by my recent activities, that we have a chance to promote our project in China's python community. hence I choose to support this immediately. |
Currently, purescript-python will automatically download this repo(called mirror) for mapping a purescript library to a git repo for providing Python FFI.
However, with only one mirror, we cannot test adding new FFI repos, because changes of this mirror could affect the regular use.
For this perspective I'd suggest adding a new dedicated mirror for testing.
@vanceism7 Also, you can just push the changes to master branch of unregistered FFI provider repos like
The text was updated successfully, but these errors were encountered: