[Scons-users] installing scons via `pip install scons` doesn't work.

Discussion:

Stefan Seefeld

2016-08-28 22:14:33 UTC

Hello,

I'm trying to install scons via `pip install scons`, and get the
following cryptic error:

$ pip install scons
Collecting scons
Using cached scons-2.5.0.tar.gz
Installing collected packages: scons
Running setup.py install for scons ... error
Complete output from command /usr/bin/python -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-build-UnhHp6/scons/setup.py';exec(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__,
'exec'))" install --record /tmp/pip-zIuAOx-record/install-record.txt
--single-version-externally-managed --compile:
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help

error: option --single-version-externally-managed not recognized

Any idea what is causing this, and how to fix it ?

Thanks,

Stefan

PS: I'm actually trying to upgrade to a newer version of scons in a
travis-ci environment (the default version is 2.3.0 - too old for me as
it doesn't support clang), and so I hoped that `pip` would be able to
help...

--
...ich hab' noch einen Koffer in Berlin...

Bill Deegan

2016-08-29 00:20:53 UTC

Permalink

Seems that pip inside a virtualenv works.
But not outside.
I think that's the current situation.

Also any way to tell what version of pip is being run?

-Bill

Post by Stefan Seefeld
Hello,
I'm trying to install scons via `pip install scons`, and get the
$ pip install scons
Collecting scons
Using cached scons-2.5.0.tar.gz
Installing collected packages: scons
Running setup.py install for scons ... error
Complete output from command /usr/bin/python -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-build-UnhHp6/scons/setup.py';
exec(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__,
'exec'))" install --record /tmp/pip-zIuAOx-record/install-record.txt
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: option --single-version-externally-managed not recognized
Any idea what is causing this, and how to fix it ?
Thanks,
Stefan
PS: I'm actually trying to upgrade to a newer version of scons in a
travis-ci environment (the default version is 2.3.0 - too old for me as
it doesn't support clang), and so I hoped that `pip` would be able to
help...
--
...ich hab' noch einen Koffer in Berlin...
_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

Stefan Seefeld

2016-08-29 00:28:42 UTC

Permalink

Post by Bill Deegan
Seems that pip inside a virtualenv works.
But not outside.
I think that's the current situation.

Any idea what the cause of the issue is ? Where is that
"--single-version-externally-managed" option coming from ?

Post by Bill Deegan
Also any way to tell what version of pip is being run?

I don't know about the travis environment (which runs trusty), but I can
reproduce the issue locally, with python 2.7 & pip 8.1.2.

Stefan

Post by Bill Deegan
-Bill
Hello,
I'm trying to install scons via `pip install scons`, and get the
$ pip install scons
Collecting scons
Using cached scons-2.5.0.tar.gz
Installing collected packages: scons
Running setup.py install for scons ... error
Complete output from command /usr/bin/python -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-build-UnhHp6/scons/setup.py';exec(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__,
'exec'))" install --record /tmp/pip-zIuAOx-record/install-record.txt
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: option --single-version-externally-managed not recognized
Any idea what is causing this, and how to fix it ?
Thanks,
Stefan
PS: I'm actually trying to upgrade to a newer version of scons in a
travis-ci environment (the default version is 2.3.0 - too old for me as
it doesn't support clang), and so I hoped that `pip` would be able to
help...
--
...ich hab' noch einen Koffer in Berlin...
_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users
<https://pairlist4.pair.net/mailman/listinfo/scons-users>
_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

--
...ich hab' noch einen Koffer in Berlin...

Daniel Holth

2016-08-29 00:30:15 UTC

Permalink

I have published a special version called import_scons that's a wheel. It
doesn't install the script so you have to say python -m SCons to run. Maybe
it will be easier to get going.

Post by Bill Deegan
Seems that pip inside a virtualenv works.
But not outside.
I think that's the current situation.
Also any way to tell what version of pip is being run?
-Bill

Post by Stefan Seefeld
Hello,
I'm trying to install scons via `pip install scons`, and get the
$ pip install scons
Collecting scons
Using cached scons-2.5.0.tar.gz
Installing collected packages: scons
Running setup.py install for scons ... error
Complete output from command /usr/bin/python -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-build-UnhHp6/scons/setup.py';exec(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__,
'exec'))" install --record /tmp/pip-zIuAOx-record/install-record.txt
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: option --single-version-externally-managed not recognized
Any idea what is causing this, and how to fix it ?
Thanks,
Stefan
PS: I'm actually trying to upgrade to a newer version of scons in a
travis-ci environment (the default version is 2.3.0 - too old for me as
it doesn't support clang), and so I hoped that `pip` would be able to
help...
--
...ich hab' noch einen Koffer in Berlin...
_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

Bill Deegan

2016-08-29 19:26:27 UTC

Permalink

Daniel,

Any chance you'd take a pass at fixing the setup.py in SCons?

-Bill

Post by Daniel Holth
I have published a special version called import_scons that's a wheel. It
doesn't install the script so you have to say python -m SCons to run. Maybe
it will be easier to get going.

Post by Bill Deegan
Seems that pip inside a virtualenv works.
But not outside.
I think that's the current situation.
Also any way to tell what version of pip is being run?
-Bill

_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

Daniel Holth

2016-08-30 01:32:58 UTC

Permalink

There's the code I used to put SCons in a wheel starting from the source
archives it makes currently. It would require minor changes to work with
enscons 0.5.0. https://bitbucket.org/dholth/scons-wheel/src/tip/SConstruct .
It finds the files, puts them in the root of the wheel and it'll get
installed into site-packages, and depending on a flag it puts different
code in a Python 3 wheel. If you want multiple versions then virtualenv is
there for you. If you wanted more "creative" installs then you might prefer
to do that during the installation of the wheel instead of baking into the
wheel itself.

Long story short if you are okay with dropping a lot of features from
setup.py and re-implementing it just in SCons as a more typical Python
package I would be up for that. What do you really need setup.py to do?

Post by Bill Deegan
Daniel,
Any chance you'd take a pass at fixing the setup.py in SCons?
-Bill

Post by Bill Deegan
Seems that pip inside a virtualenv works.
But not outside.
I think that's the current situation.
Also any way to tell what version of pip is being run?
-Bill

Post by Stefan Seefeld
Hello,
I'm trying to install scons via `pip install scons`, and get the
$ pip install scons
Collecting scons
Using cached scons-2.5.0.tar.gz
Installing collected packages: scons
Running setup.py install for scons ... error
Complete output from command /usr/bin/python -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-build-UnhHp6/scons/setup.py';exec(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__,
'exec'))" install --record /tmp/pip-zIuAOx-record/install-record.txt
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: option --single-version-externally-managed not recognized
Any idea what is causing this, and how to fix it ?
Thanks,
Stefan
PS: I'm actually trying to upgrade to a newer version of scons in a
travis-ci environment (the default version is 2.3.0 - too old for me as
it doesn't support clang), and so I hoped that `pip` would be able to
help...
--
...ich hab' noch einen Koffer in Berlin...
_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

Bill Deegan

2017-12-01 18:31:33 UTC

Permalink

Picking this back up.

I'm o.k. with dropping everything in existing setup.py to fix pypi install.
I've started work on creating a vanilla setup.py but I'm a newbie at this
so any help would be welcome.
Ideally we'd be able to use pip install -e against the git checkout, create
pypi packages (wheel seems to be the correct thing today).

Currently bootstrap.py add version strings to all the source files, I'm
pretty sure there's no "legal" reason to update the copyright date in each
file.

We would like to keep building the scons-local packages, but setup.py is
not really needed to do that.

Use console_scripts to build the scons, sconsign, and other scripts so it
will use the correct version of python.

thoughts?
-Bill

Post by Daniel Holth
There's the code I used to put SCons in a wheel starting from the source
archives it makes currently. It would require minor changes to work with
enscons 0.5.0. https://bitbucket.org/dholth/scons-wheel/src/tip/SConstruct .
It finds the files, puts them in the root of the wheel and it'll get
installed into site-packages, and depending on a flag it puts different
code in a Python 3 wheel. If you want multiple versions then virtualenv is
there for you. If you wanted more "creative" installs then you might prefer
to do that during the installation of the wheel instead of baking into the
wheel itself.
Long story short if you are okay with dropping a lot of features from
setup.py and re-implementing it just in SCons as a more typical Python
package I would be up for that. What do you really need setup.py to do?

Post by Bill Deegan
Daniel,
Any chance you'd take a pass at fixing the setup.py in SCons?
-Bill

Post by Daniel Holth
I have published a special version called import_scons that's a wheel.
It doesn't install the script so you have to say python -m SCons to run.
Maybe it will be easier to get going.

Post by Bill Deegan
Seems that pip inside a virtualenv works.
But not outside.
I think that's the current situation.
Also any way to tell what version of pip is being run?
-Bill

_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

Daniel Holth

2017-12-01 18:55:52 UTC

Permalink

Sounds good to me.

Post by Bill Deegan
Picking this back up.
I'm o.k. with dropping everything in existing setup.py to fix pypi install.
I've started work on creating a vanilla setup.py but I'm a newbie at this
so any help would be welcome.
Ideally we'd be able to use pip install -e against the git checkout,
create pypi packages (wheel seems to be the correct thing today).
Currently bootstrap.py add version strings to all the source files, I'm
pretty sure there's no "legal" reason to update the copyright date in each
file.
We would like to keep building the scons-local packages, but setup.py is
not really needed to do that.
Use console_scripts to build the scons, sconsign, and other scripts so it
will use the correct version of python.
thoughts?
-Bill

Post by Daniel Holth
There's the code I used to put SCons in a wheel starting from the source
archives it makes currently. It would require minor changes to work with
enscons 0.5.0.
https://bitbucket.org/dholth/scons-wheel/src/tip/SConstruct . It finds
the files, puts them in the root of the wheel and it'll get installed into
site-packages, and depending on a flag it puts different code in a Python 3
wheel. If you want multiple versions then virtualenv is there for you. If
you wanted more "creative" installs then you might prefer to do that during
the installation of the wheel instead of baking into the wheel itself.
Long story short if you are okay with dropping a lot of features from
setup.py and re-implementing it just in SCons as a more typical Python
package I would be up for that. What do you really need setup.py to do?

Post by Bill Deegan
Daniel,
Any chance you'd take a pass at fixing the setup.py in SCons?
-Bill

Post by Daniel Holth
I have published a special version called import_scons that's a wheel.
It doesn't install the script so you have to say python -m SCons to run.
Maybe it will be easier to get going.

Post by Bill Deegan
Seems that pip inside a virtualenv works.
But not outside.
I think that's the current situation.
Also any way to tell what version of pip is being run?
-Bill

Post by Stefan Seefeld
Hello,
I'm trying to install scons via `pip install scons`, and get the
$ pip install scons
Collecting scons
Using cached scons-2.5.0.tar.gz
Installing collected packages: scons
Running setup.py install for scons ... error
Complete output from command /usr/bin/python -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-build-UnhHp6/scons/setup.py';exec(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__,
'exec'))" install --record /tmp/pip-zIuAOx-record/install-record.txt
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: option --single-version-externally-managed not recognized
Any idea what is causing this, and how to fix it ?
Thanks,
Stefan
PS: I'm actually trying to upgrade to a newer version of scons in a
travis-ci environment (the default version is 2.3.0 - too old for me as
it doesn't support clang), and so I hoped that `pip` would be able to
help...
--
...ich hab' noch einen Koffer in Berlin...
_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

Bill Deegan

2017-12-01 21:24:46 UTC

Permalink

What's the best way to collaborate?
I can create a branch in my repo and you fork it?

-Bill

Post by Daniel Holth
Sounds good to me.

Post by Daniel Holth
There's the code I used to put SCons in a wheel starting from the source
archives it makes currently. It would require minor changes to work with
enscons 0.5.0. https://bitbucket.org/dholth/
scons-wheel/src/tip/SConstruct . It finds the files, puts them in the
root of the wheel and it'll get installed into site-packages, and depending
on a flag it puts different code in a Python 3 wheel. If you want multiple
versions then virtualenv is there for you. If you wanted more "creative"
installs then you might prefer to do that during the installation of the
wheel instead of baking into the wheel itself.
Long story short if you are okay with dropping a lot of features from
setup.py and re-implementing it just in SCons as a more typical Python
package I would be up for that. What do you really need setup.py to do?

Post by Bill Deegan
Daniel,
Any chance you'd take a pass at fixing the setup.py in SCons?
-Bill

Post by Daniel Holth
I have published a special version called import_scons that's a wheel.
It doesn't install the script so you have to say python -m SCons to run.
Maybe it will be easier to get going.

Post by Bill Deegan
Seems that pip inside a virtualenv works.
But not outside.
I think that's the current situation.
Also any way to tell what version of pip is being run?
-Bill

_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

Bill Deegan

2017-12-01 21:47:56 UTC

Permalink

Is there a simple way to filter out files by name when packaging?

So we have
src/engine/SCons/Taskmaster.py
src/engine/SCons/TaskmasterTests.py

I'd like to not package any of the *Tests.py files.

-Bill

Post by Bill Deegan
What's the best way to collaborate?
I can create a branch in my repo and you fork it?
-Bill

Post by Daniel Holth
Sounds good to me.

Post by Bill Deegan
Picking this back up.
I'm o.k. with dropping everything in existing setup.py to fix pypi install.
I've started work on creating a vanilla setup.py but I'm a newbie at
this so any help would be welcome.
Ideally we'd be able to use pip install -e against the git checkout,
create pypi packages (wheel seems to be the correct thing today).
Currently bootstrap.py add version strings to all the source files, I'm
pretty sure there's no "legal" reason to update the copyright date in each
file.
We would like to keep building the scons-local packages, but setup.py is
not really needed to do that.
Use console_scripts to build the scons, sconsign, and other scripts so
it will use the correct version of python.
thoughts?
-Bill

Post by Daniel Holth
There's the code I used to put SCons in a wheel starting from the
source archives it makes currently. It would require minor changes to work
with enscons 0.5.0. https://bitbucket.org/dholth/s
cons-wheel/src/tip/SConstruct . It finds the files, puts them in the
root of the wheel and it'll get installed into site-packages, and depending
on a flag it puts different code in a Python 3 wheel. If you want multiple
versions then virtualenv is there for you. If you wanted more "creative"
installs then you might prefer to do that during the installation of the
wheel instead of baking into the wheel itself.
Long story short if you are okay with dropping a lot of features from
setup.py and re-implementing it just in SCons as a more typical Python
package I would be up for that. What do you really need setup.py to do?

Post by Bill Deegan
Daniel,
Any chance you'd take a pass at fixing the setup.py in SCons?
-Bill

Post by Daniel Holth
I have published a special version called import_scons that's a
wheel. It doesn't install the script so you have to say python -m SCons to
run. Maybe it will be easier to get going.

Post by Bill Deegan
Seems that pip inside a virtualenv works.
But not outside.
I think that's the current situation.
Also any way to tell what version of pip is being run?
-Bill

Post by Stefan Seefeld
Hello,
I'm trying to install scons via `pip install scons`, and get the
$ pip install scons
Collecting scons
Using cached scons-2.5.0.tar.gz
Installing collected packages: scons
Running setup.py install for scons ... error
Complete output from command /usr/bin/python -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-build-UnhHp6/scons/setup.py';exe
c(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__,
'exec'))" install --record /tmp/pip-zIuAOx-record/install
-record.txt
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: option --single-version-externally-managed not recognized
Any idea what is causing this, and how to fix it ?
Thanks,
Stefan
PS: I'm actually trying to upgrade to a newer version of scons in a
travis-ci environment (the default version is 2.3.0 - too old for me as
it doesn't support clang), and so I hoped that `pip` would be able to
help...
--
...ich hab' noch einen Koffer in Berlin...
_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

_______________________________________________
Scons-users mailing list
https://pairlist4.pair.net/mailman/listinfo/scons-users

Mats Wichmann

2017-12-03 15:00:10 UTC

Permalink

Post by Bill Deegan
Is there a simple way to filter out files by name when packaging?
So we have
src/engine/SCons/Taskmaster.py
src/engine/SCons/TaskmasterTests.py
I'd like to not package any of the *Tests.py files.

there's an exclude_package_data dictionary for this.

Bill Deegan

2017-12-05 00:04:51 UTC

Permalink

Is there a way to say:

Exclude .xml files in all packages except SCons.Tool.docbook, in which case
include all files.

Post by Mats Wichmann

there's an exclude_package_data dictionary for this.

Mats Wichmann

2017-12-06 15:23:42 UTC

Permalink

Post by Bill Deegan
Exclude .xml files in all packages except SCons.Tool.docbook, in which case
include all files.

I can't tell, because I don't precisely know who "wins".

exclude_package_data=['':['*.xml']]
package_data=[
...,
'SCons.Tool.docbook':[*.xml']
}

would seem to describe it, but if exclude_package_data is always applied
even if something is listed in package_data (as the docs I just looked
at hint at), you would have to do it the other way - list all the
packages that are not docbook in exclude_package_data instead.