On Thu, Mar 19, 2015 at 10:38 PM, Nick Coghlan ncogh...@gmail.com wrote:
I believe setuptools can already do this (as setup-requirements.txt),
but it's a generated file that people tend not to check into source control.
Isn't that just some project's convention - they just read it up in
On Thu, Mar 19, 2015 at 9:45 AM, Tim Smith t...@tim-smith.us wrote:
A way of learning about setup_requires dependencies would be helpful for
homebrew-pypi-poet [1], which helps generate Homebrew formulae for
applications implemented in Python.
Indeed -- conda is similar -- it provides a
On 19 March 2015 at 08:15, Donald Stufft don...@stufft.io wrote:
If you’re using a script this doesn’t effect you, JSONP and CORS are two
methods for allowing the javascript on example.com to access a JSON URL on
example.net. They are ways of getting around the fact that the browser doesn't
On 19 March 2015 at 02:57, Donald Stufft don...@stufft.io wrote:
For awhile now PyPI has supported JSONP on the /pypi/*/json API to allow
people
to access the JSON data in a cross origin request. JSONP is problematic psuedo
standard which has niggly edge cases which make it hard to fully
On Mar 19, 2015, at 4:12 AM, Paul Moore p.f.mo...@gmail.com wrote:
On 19 March 2015 at 02:57, Donald Stufft don...@stufft.io wrote:
For awhile now PyPI has supported JSONP on the /pypi/*/json API to allow
people
to access the JSON data in a cross origin request. JSONP is problematic
On 19 March 2015 at 16:46, Chris Barker chris.bar...@noaa.gov wrote:
I guess I have no idea if there was a big problem with the architecture of
setuptools requiring a big shift -- all I see are problems with the API and
feature set.and by definition you can't change those and be backward
If that's what you want then we could say the spec was to put the
requirements in setup_requires.txt, in the requirements.txt format,
which pip would eventually look for and install before running
setup.py
On Thu, Mar 19, 2015 at 9:32 AM, Leonardo Rochael Almeida
leoroch...@gmail.com wrote:
On
... except that there are plenty of reasons we wouldn't want the
requirements.txt format, mainly because pip shouldn't automatically
install concrete dependencies that contain git:// urls etc.
On Thu, Mar 19, 2015 at 9:57 AM, Daniel Holth dho...@gmail.com wrote:
If that's what you want then we
On 18 March 2015 at 14:37, Daniel Holth dho...@gmail.com wrote:
[...]
The behavior we're aiming for would be:
installer run setup.py - installs things
python setup.py - does not install things
Besides that, I'd add that we're also looking for: python setup.py (by
itself) should not raise
On Thu, Mar 19, 2015 at 9:26 AM, Ionel Cristian Mărieș cont...@ionelmc.ro
wrote:
The --record is for making a list of installed files. You don't need it if
you don't use record.txt anywhere.
thanks -- Ill take that out... This was a cut and paste form teh net after
much frustration -- once I
On Thu, Mar 19, 2015 at 7:12 AM, Daniel Holth dho...@gmail.com wrote:
So I'd like to suggest the following series of small improvements to both
pip and setuptools:
* setuptools: `python setup.py setup_requires` dumps its setup_requires
keyword in 'requirements.txt' format
It's is already
The reason you should not have to run setup.py to dump out the
setup-requires is that, in the what-people-tend-to-expect definition,
setup.py cannot run without those requirements being installed first.
There is a similar problem with putting setup-requires in the PEP 426
Metadata. As long as we
Apologies: misattributed Leonardo Rochael Almeida leoroch...@gmail.com's
comments to Daniel Holth when I was cutting and pasting from my digest.
On Thu, Mar 19, 2015 at 9:45 AM, Tim Smith t...@tim-smith.us wrote:
On Thu, Mar 19, 2015 at 7:12 AM, Daniel Holth dho...@gmail.com wrote:
So I'd
On 19 Mar 2015 23:33, Leonardo Rochael Almeida leoroch...@gmail.com
wrote:
On 18 March 2015 at 14:37, Daniel Holth dho...@gmail.com wrote:
[...]
The behavior we're aiming for would be:
installer run setup.py - installs things
python setup.py - does not install things
Besides that, I'd
On Thu, Mar 19, 2015 at 9:56 AM, Chris Barker chris.bar...@noaa.gov wrote:
On Thu, Mar 19, 2015 at 9:26 AM, Ionel Cristian Mărieș cont...@ionelmc.ro
wrote:
The --record is for making a list of installed files. You don't need it
if you don't use record.txt anywhere.
thanks -- Ill take
On Thu, Mar 19, 2015 at 9:12 AM, Ionel Cristian Mărieș cont...@ionelmc.ro
wrote:
Worth considering, if you can afford it, to have a local patch that you
apply before building. Then you have all the necessary fixes (like remove
the setup_requires) in that patch file.
yup -- that's a option
On Thu, Mar 19, 2015 at 6:57 AM, Daniel Holth dho...@gmail.com wrote:
If that's what you want then we could say the spec was to put the
requirements in setup_requires.txt, in the requirements.txt format,
which pip would eventually look for and install before running
setup.py
yes, that would
The --record is for making a list of installed files. You don't need it if
you don't use record.txt anywhere.
As for --single-version-externally-managed, that's unrelated to your
setup_requires pain - you probably already have the eggs around, so they
aren't redownloaded. What
On Wed, Mar 18, 2015 at 10:37 AM, Daniel Holth dho...@gmail.com wrote:
The behavior we're aiming for would be:
installer run setup.py - installs things
python setup.py - does not install things
yup.
Which, now that I look at it, is not so different than:
python setup.py build # does not
On Thu, Mar 19, 2015 at 7:12 AM, Daniel Holth dho...@gmail.com wrote:
... except that there are plenty of reasons we wouldn't want the
requirements.txt format, mainly because pip shouldn't automatically
install concrete dependencies that contain git:// urls etc.
is that format problem, or a
On Thu, Mar 19, 2015 at 5:38 PM, Chris Barker chris.bar...@noaa.gov wrote:
My use case at the moment is trying to build conda packages from other
peoples' Python packages - if they use setup_requires, etc, then I'm stuck
with it.
Worth considering, if you can afford it, to have a local
On Wed, Mar 18, 2015 at 9:02 AM, Ionel Cristian Mărieș cont...@ionelmc.ro
wrote:
On Wed, Mar 18, 2015 at 5:33 PM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
I don't want it downloading and installing dependencies when I go to
build. That's an install- time task.
Sounds to
On Wed, Mar 18, 2015 at 8:43 AM, Paul Moore p.f.mo...@gmail.com wrote:
I suppose it's too late now, but the really painful parts of all this
seem to be due to overly aggressive backward compatibility. We now
have wheels, but also eggs, we now have pip, but also easy_install,
etc.
23 matches
Mail list logo
