-
Notifications
You must be signed in to change notification settings - Fork 71
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
Current version in git installer seems broken #46
Comments
I think the breaking commit is d4dc083 |
Ah, yeah, thanks for this issue! I think the problem is a missing MANIFEST.in entry or something like that. I'll make a new pypi release hopefully today. If not today, then definitely tomorrow. |
Coo. For the moment, I just got lazy and vendored the whole library. It works fine from the git folder. Having this makes my life a lot easier, thanks for releasing it! As a side-note, the 20x4 test python file is broken:
Neither of the above are 4x20, but that was easy to fix. |
Release 0.9.0 is out on PyPI! A simple |
Sure, that's fine. If you want, you can now check out the
Great to hear :)
Oh, thanks for letting me know. I'll fix :) |
Wait, did you go from 0.4.0 to 0.9.0? What happened to 0.5.0 - 0.8.0? |
Yep, I plan to release 1.0.0 soon, and 0.9.0 is something like the "release candidate". |
Thanks @fake-name for reporting this in #46.
Heh, I see. I kind of guessed it was something like that. It sure seems a hell of a lot more stable then most raspberry pi stuff I've run across. |
Thanks! That was one of my main goals. Most scripts for the Pi are copy-pasted from some tutorials and consist of very hacky code. I wanted something clean and pythonic, with an easy API. |
Just installed from github, it seems to work fine. Only complaint I have at this point is there's no |
You can check |
The issue I had here was more "Ok, I /think/ it installed over my manual version, how do I verify what version I'm running". Basically, I had a installed instance that seemed to work, but I wasn't sure if it was actually the one from pypi or one I installed manually. Once the package is installed, there doesn't seem to be an easy way to determine the version, short of finding the module location and looking in the source file/at the egg manually. It's a minor issue, though. |
On a fresh install from git:
Somehow, the
codecs
directory isn't getting created. I suspect that the setuptools dependency resolution isn't detecting the codecs files.I manually cloned the repository, and the problem still occurs:
The text was updated successfully, but these errors were encountered: