[Scons-users] SCons 3.0.0.alpha.20170614 available on testpypi

[Bill Deegan]

O.k. it will work if you do the following:

virtualenv venv
venv/bin/pip install -i https://testpypi.python.org/pypi scons
. venv/bin/activate
scons --version

Assuming the virtualenv is the one for the version of python you wish to
use (python 2.7.x, 3.5.x, 3.6.x)

However if you don't activate the virtualenv and then run:
venv/bin/scons

And the virtualenv is not for the python found via `which python`, then it
will fail with something like:
SCons import failed. Unable to find engine files in:
  /Users/bdbaddog/tmp/venv35/bin/../engine
  /Users/bdbaddog/tmp/venv35/bin/scons-local-3.0.0.alpha.20170614
  /Users/bdbaddog/tmp/venv35/bin/scons-local
  /Users/bdbaddog/tmp/venv35/lib/scons-3.0.0.alpha.20170614

/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/scons-3.0.0.alpha.20170614

/Users/bdbaddog/tmp/venv35/lib/python2.7/site-packages/scons-3.0.0.alpha.20170614

/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/scons-3.0.0.alpha.20170614

/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/scons-3.0.0.alpha.20170614
  /Users/bdbaddog/tmp/venv35/lib/scons
  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/scons
  /Users/bdbaddog/tmp/venv35/lib/python2.7/site-packages/scons

/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/scons
  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/scons
Traceback (most recent call last):
  File "venv35/bin/scons", line 192, in <module>
    import SCons.Script
ImportError: No module named SCons.Script

Please give it a try and send any feedback to the users mailing list.

Thanks,
Bill
SCons Co-Manager

On Wed, Jun 14, 2017 at 4:55 PM, Bill Deegan <bill at baddogconsulting.com>
wrote:

> Hold off a bit.
> Seems there's an issue running under py35 or py36 virtualenv.
>
> I'll report back when that's resolved.
>
> If you want to try under py 27, go ahead.
> Make sure you've updated your virtualenv and pip
> pip install -U virtualenv pip
> virtualenv venv
> venv/bin/pip install -i https://testpypi.python.org/pypi scons
>
> Should do the trick.
> -Bill
>
> On Wed, Jun 14, 2017 at 4:49 PM, Bill Deegan <bill at baddogconsulting.com>
> wrote:
>
>> Greetings,
>>
>> This is an alpha quality release.
>> It's the first version to support both python 3.5+, 2.7.x, and pypy.
>> There have been 701 commits since the 2.5.1 release.
>>
>> Please report any issues to the scons-users mailing list.
>> (See: http://scons.org/lists.html )
>>
>>
>> You can download via:
>> pip install -i https://testpypi.python.org/pypi scons
>>
>> Please do so in a virtualenv and not in your python distro.
>>
>> RELEASE 3.0.0.alpha.20170614 - Mon, 14 Jun 2017 12:23:56 -0400
>>
>>   Please consult the RELEASE.txt file for a summary of changes since the
>> last
>>   release and consult the CHANGES.txt file for complete a list of changes
>>   since last release.  This announcement highlights only the important
>>   changes.
>>     Please note the following important changes since release 2.5.1:
>>        *IT IS NOT READY FOR PRODUCTION USE*
>>
>>        This is the initial release supporting both python 3.5+ and 2.7.x
>> and pypy
>>        There are some important changes:
>>
>>        - Any print statements must now use python 3 syntax of "print()"
>>        - All node content should be in bytes. This is the default in
>> python 2.7.x,
>>          in Python 3 all strings are by default unicode. byte and/or
>> bytearray
>>          should be used if you construct content for return by a custom
>> node type's
>>          get_content() method.
>>        - This is some (as yet unresolved issue) using Literal()'s in some
>> context with
>>          Python 3
>>        - pypy should be supported, please report any issues to the user's
>> mailing list.
>>        - Currently if you switch back and forth between python 2.7.x and
>> 3.5+ you will
>>          need to remove your sconsign file.  This should be resolves
>> shortly, but
>>          regardless switching between python 2.7.x and 3.5+ will not use
>> compatible
>>          sconsigns and as such incremental builds should be expected to
>> rebuild
>>          anything changed since the previous scons run with the same
>> version of python.
>>        - It is likely that migrating from 2.5.1 -> 3.0.0 alpha will cause
>> rebuilds due
>>          to the significant number of changes in the codebase.
>>
>>        - Removed deprecated tools CVS, Perforce, BitKeeper, RCS, SCCS,
>> Subversion.
>>        - Removed deprecated module SCons.Sig
>>        - See CHANGES.txt for more details on other changes
>>        - 3.0.0 should be slightly faster than 2.5.1.  Changes yielded a
>> 15% speed up for
>>          null incremental builds.
>>        - Updated D language scanner support to latest: 2.071.1.
>>        - python -m SCons should now run SCons if it's installed PYTHONPATH
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20170614/434076f2/attachment.html>