-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
prep for release 1.3 #18
Comments
I think it would be good to standardize on a code style/linter; I like flake8 (with a few rules turned off), and 4 spaces instead of 2. I'll submit another PR with my suggestions. edit: #19 |
All of the things identified for 1.3 release have been done. @logan-pugh you've done most of the new feature work, do you see anything else that should be done before making a release? |
I pushed a release candidate 1.3.0rc tag. |
I tried this version with pyinstaller and got the failure below during runtime. File "site-packages\archook_init_.py", line 14, in |
@jesegal nope, not jumping the gun, please open as a a new issue though. |
@mhw-at-yg Any updates on this? I dutifully followed advice from #31 embedding this neat tool into my own packages and products, and it is working great. As of now though, the PyPi version is still |
thanks for the nudge @cooperjaXC . I've added this to my to-look-at for tomorrow |
@cooperjaXC if you pip install from github does that still work for you? I'm not making much headway against #34, but maybe that only affects conda users like myself and isn't a general issue.
|
@maphew It works fine for me, but I don't |
Hello, new maintainer Matt Wilkie here. I'm planning to issue a new release, chiefly to take advantage of the support for ArcGIS Pro from #16 courtesy of @logan-pugh. Please raise anything you think should be addressed or included, either as comment here or new issue.
I treat 1st comment as wiki and update periodically to reflect issue status
The text was updated successfully, but these errors were encountered: