Skip to content
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

Allow for release on pypi by applying diff from althonos/fs.smbfs#11 as a monkeypatch #33

Closed

Conversation

telamonian
Copy link
Collaborator

fixes #32

Haven't head back from @althonos about althonos/fs.smbfs#11, so I'm going to go ahead and publish 0.0.2 using a workaround. Not the prettiest solution in the world, but probably the simplest. Pull in the real fs.smbfs in setup.py and then applies the diff from my PR as a monkeypatch.

Once this gets pulled in we'll be able to actually complete the release of 0.0.2 to pypi (I already did a release to test pypi and it went through perfectly).

@telamonian telamonian requested a review from timkpaine May 13, 2020 20:12
@telamonian
Copy link
Collaborator Author

Also, here's the results from the windows ci on fdea8a4. It's passing, which shows that the monkeypatch in this PR is indeed fixing the same bug as the althonos/fs.smbfs#11 PR itself

@telamonian
Copy link
Collaborator Author

Woo! 20 minutes after I opened this PR althonos/fs.smbfs#11 finally got merged in. It's now part of the fs.smbfs@0.6.2 release

@telamonian telamonian closed this May 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The 0.0.2 release is blocked by althonos/fs.smbfs#11
1 participant