Closed ompadu closed 7 years ago
No Python 3.6 support. I've missed that. My bad. That's why it failed.
Hi! Yes that's related to #186. It's only due to the automatic target name deduction which behaves different in Python 3.6. If you give every target a name, it works.
Thanks for the workaround!
I see that the 3.x branch targets Py3.6 but is there any chance a fix would come into 2.x? And while we are on the 3.x subject, will that branch eventually support setuptools or target nodepy only?
The 3.x branch will be a whole new version of Craftr :^) I do plan to fix #186 for Craftr 2.x though. Hopefully very soon.
Oh and for the time being, Craftr 3.x is not planned to be installable via setuptools, however it may be possible to make setup.py
install Node.py and then proceed with the installation. That is for the future though, and when 3.x is usable.
It appears it was simpler than I thought it would be to fix #186. Until there is no version with the fix on PyPI, you can simply upgrade the nr
package.
$ pip install --upgrade 'nr>=1.4.7'
Platform: Windows 10.0.15063 x64 Visual Studio version: 15.3.4 Python version: 3.6.2 craftr version: 2.0.0
After I've installed craftr with "pip install craftr-build==2.0.0", I've downloaded the craftr v.2.0.0 release, opened the "x64 Native Tools Command Prompt for VS 2017", navigated to the example.c folder and tried to run craftr export. It failed with the following output:
example.cpp "craftr export" fails with the same output. For example.csharp both export and build work.