On Fri, 2 Sep 2016 at 22:06 Nick Coghlan wrote:
> On 2 September 2016 at 19:28, Paul Moore wrote:
> > On 2 September 2016 at 09:58, Sylvain Corlay
> wrote:
> >> My point here was that I don't think that the proposed feature has much
> to
> >> do with the concerns that were raised about distutil
#x27;), ('py30', 'none', 'any')
>
> Enscons would let you control the wheel tag directly but doesn't yet let
> you build multiple wheels with a single invocation.
>
> On Mon, Aug 29, 2016, 19:46 Donald Stufft wrote:
>
>
> On Aug 29, 2016, at 7:
Someone has asked that I do a new release of importlib that includes a
LICENSE file on PyPI: https://pypi.org/project/importlib/. Historically I
have had the setup.py simply not include any Python code when built on
versions of Python that include importlib in the stdlib itself:
https://github.com/
cision
on how to handle it long-term.
-Brett
>
> Thanks,
>
> Sylvain
>
> On Mon, Aug 29, 2016 at 12:36 AM, Paul Moore wrote:
>
>> On 28 August 2016 at 18:05, Brett Cannon wrote:
>> > The discussion of Sylvain's proposed changes to distutils suggests that
The discussion of Sylvain's proposed changes to distutils suggests that
there isn't a clear-cut agreement or position of this SIG -- and thus
Python -- on changes to distutils, its future, etc. Is there an official
position I'm not aware of? If not, could we get one so we know how to
handle any mor
On Tue, 23 Aug 2016 at 07:33 Donald Stufft wrote:
>
> > On Aug 23, 2016, at 7:25 AM, Nick Coghlan wrote:
> >
> > OK, cool - that gives us all the more reason to retain bdist_wininst
> > and bdist_msi hosting support. However, I do think it makes sense for
> > us to say up front that we'll recons
On Fri, 19 Aug 2016 at 12:53 Donald Stufft wrote:
>
> On Aug 19, 2016, at 2:00 PM, Leonardo Rochael Almeida <
> leoroch...@gmail.com> wrote:
>
> ure, more people will be affected this way than just the folks releasing
> on Windows, but given the shortcuts for setting the sdist format per
> projec
+1 on the whole idea. Trying to continue to nudge the community towards
more standardized approaches in packaging is always a good thing. :) I only
have one data point in relation to sdists file formats.
On Mon, 15 Aug 2016 at 12:09 Donald Stufft wrote:
> [SNIP]
>
> Looking at numbers again, the
On Sat, 23 Jul 2016 at 10:36 Daniel Holth wrote:
> Not yet. Someone should fix that 😎
>
There is an issue tracking that if someone gets adventurous enough to write
up a PR: https://github.com/pypa/pip/issues/3691 .
-Brett
>
> On Sat, Jul 23, 2016, 11:37 Alex Grönholm
> wrote:
>
>> pip doesn't
On Tue, 12 Jul 2016 at 21:54 Donald Stufft wrote:
>
> > On Jul 12, 2016, at 4:45 PM, Glyph Lefkowitz
> wrote:
> >
> > My feeling is that there should be a "dead man's switch" sort of
> mechanism for this. Require manual intervention from at least one package
> owner at least once a year. I bel
On Fri, 10 Jun 2016 at 07:25 Ian Cordasco
wrote:
> On Fri, Jun 10, 2016 at 8:22 AM, Jason R. Coombs
> wrote:
> > In #pypa-dev, I raised the possibility of moving our PyPA support
> channels from IRC to another hosted solution that enables persistence.
> Although IRC has served us well, there are
Cool, thanks!
On Mon, 16 May 2016 at 07:49 Donald Stufft wrote:
>
> On May 16, 2016, at 10:43 AM, Brett Cannon wrote:
>
> I'm at OSCON and in a tutorial on my work laptop so I didn't have a chance
> to verify there weren't any reST errors, so if someone wit
And the PEP is checked in! https://hg.python.org/peps/file/tip/pep-0518.txt
I'm at OSCON and in a tutorial on my work laptop so I didn't have a chance
to verify there weren't any reST errors, so if someone with commit
privileges can just quickly run `make` on the peps repo to make sure I
didn't bo
ng Minimum Build System Requirements for Python Projects
Version: $Revision$
Last-Modified: $Date$
Author: Brett Cannon ,
Nathaniel Smith ,
Donald Stufft
BDFL-Delegate: Nick Coghlan
Discussions-To: distutils-sig
Status: Draft
Type: Standards Track
Content-Type: text/x-rst
Created: 1
On Fri, 13 May 2016 at 11:34 Chris Barker wrote:
> One other question:
>
> Is it just examples or is "build" being defined as "build a wheel"?
>
Just an example (clarified previously).
-Brett
>
> i.e. there are times one might want to build a package without building a
> wheel -- just it inst
On Fri, 13 May 2016 at 10:47 Paul Moore wrote:
> On 13 May 2016 at 18:15, Chris Barker wrote:
> > I think we're freaking out way too much about what *could* go wrong.
>
> It's more that:pip would have to vendor pyyaml, and it's not small. I
> have no idea whether it's easy to vendor, either (doe
On Thu, 12 May 2016 at 20:52 Nick Coghlan wrote:
> On 13 May 2016 at 02:33, Brett Cannon wrote:
> > Both Donald and Nathaniel say to drop it, and since I put it in just to
> be
> > overly cautious I'm fine with dropping it. So unless Nick says
> > "semantics-ve
On Thu, 12 May 2016 at 05:43 Donald Stufft wrote:
>
> > On May 12, 2016, at 8:31 AM, Nick Coghlan wrote:
> >
> > We could also keep semantics-version, and just put it inside
> [build-system].
> >
> > Either way, by allowing access to the [tool.*] namespace without any
> > other version check, th
On Wed, 11 May 2016 at 16:01 Nathaniel Smith wrote:
> On Wed, May 11, 2016 at 11:32 AM, Brett Cannon wrote:
> [...]
> > the file is for the project, not just the package(s) the project
> > contains ("package" is an overloaded term and I don't want to contribut
On Wed, 11 May 2016 at 12:37 Robert Collins
wrote:
> On 12 May 2016 at 06:32, Brett Cannon wrote:
> > Since you can easily read the PEP at
> > https://github.com/brettcannon/build-deps-pep in a nice, rendered
> format I
> > won't repost the whole thing, but her
's
just the same example as in the PEP but with one field changed; IOW it
doesn't really add anything. I also didn't rename the file as Randy argued
for because the file is for the project, not just the package(s) the
project contains ("package" is an overloaded term and I
ed out and look forward to this being the first step towards
allowing projects to customize their build process better!
-
PEP: NNN
Title: Specifying build dependencies for Python Software Packages
Version: $Revision$
Last-Modified: $Date$
Author: Brett Cannon ,
Nathaniel Smith ,
Just so everyone knows, I'm ignoring this thread as the PEP I'm drafting
with Donald and Nathaniel is nearly finished and thus has already settled
on the file format discussion and I haven't heard a new point made on any
file format proposal that has already been brought up previously.
On Tue, 10
On Mon, 9 May 2016 at 11:21 Chris Barker wrote:
> "pymeta" feels very "inessentially weird" to me [1].
>
>
> yeah...
>
> setup.toml
>
> ???
>
You can all stop guessing at file names. The PEP will have a recommendation
and you all can either agree or disagree at that point. Please don't give
me m
On Mon, 9 May 2016 at 06:29 Nick Coghlan wrote:
> On 9 May 2016 at 01:43, Donald Stufft wrote:
> > Overall, my suggestion here would be to have a file called
> ``pymeta.toml`` (or
> > ``meta.toml``)
>
> pymeta.toml would be fine by me.
>
> I don't really buy the "collision with Debian build tool
On Mon, 9 May 2016 at 06:42 Nick Coghlan wrote:
> On 7 May 2016 at 08:21, Paul Moore wrote:
> > On 6 May 2016 at 19:14, Brett Cannon wrote:
> >> OK, assuming the Nick will be pronouncing, who wants to write the PEP?
> >
> > ... and if Nick doesn't want to pr
Based on this email and Nathaniel's evaluation I've gone ahead and taken it
upon myself to start writing a PEP so we have something concrete to work
from. I'm hoping to have it done some time this week.
On Sun, 8 May 2016 at 08:43 Donald Stufft wrote:
>
> > On May 8, 2016, at 9:13 AM, Nick Coghl
On Sat, May 7, 2016, 15:47 Donald Stufft wrote:
>
> > On May 7, 2016, at 5:05 PM, Robert Collins
> wrote:
> >
> > Either we are defining the long term thing now, in which case that
> > huge pile of complexity lands on us, and we have to get everything
> > right.
> >
> > Or we are defining a thin
On Sat, May 7, 2016, 12:16 Chris Barker wrote:
> On Sat, May 7, 2016 at 11:18 AM, Brett Cannon wrote:
>
>> What fields there will be and their semantics ...
>>
>>1. Format version (so just deciding on a name -- which also includes
>> whether it should b
On Fri, 6 May 2016 at 16:58 Nathaniel Smith wrote:
> On Fri, May 6, 2016 at 11:14 AM, Brett Cannon wrote:
> >
> >
> > On Fri, 6 May 2016 at 09:40 Donald Stufft wrote:
> >>
> >>
> >> On May 6, 2016, at 12:36 PM, Brett Cannon wrote:
> >&
On Sat, 7 May 2016 at 07:49 Nick Coghlan wrote:
>
> On 7 May 2016 13:00, "Nathaniel Smith" wrote:
> >
> > Here's that one-stop writeup/comparison of all the major configuration
> > languages that I mentioned:
> >
> > https://gist.github.com/njsmith/78f68204c5d969f8c8bc645ef77d4a8f
>
> Thanks for
On Fri, 6 May 2016 at 09:40 Donald Stufft wrote:
>
> On May 6, 2016, at 12:36 PM, Brett Cannon wrote:
>
> So who is the BDFL on this decision? It seems we need someone to stop the
> bikeshedding on the field name and what file is going to house this
> configuration data. And
The emails seem to have reached an equilibrium point of bikeshedding on the
(bootstrap|setup)_requires issue that is being discussed (as Daniel points
out below, this has nothing to do with how building works and instead is
only about statically declaring what tools need to be installed to simply
r
Thanks for the update! Glad this is still moving forward. I'll continue to
prod the list if things stall again as I want to respond to "Python
packaging is broken" with "actually your knowledge is just outdated, go
read packaging.python.org". :)
On Tue, 3 May 2016 at 11:28 Nathaniel Smith wrote:
On Wed, 27 Apr 2016 at 10:53 Donald Stufft wrote:
> This isn't really a problem with what you're doing. Rather it's an issue
> with the toolchain and and open question whether or not wheels should
> conceptually be able to be produced from a checkout, or if they should only
> be produced from a s
https://packaging.python.org/en/latest/ should have all the information you
need to learn how to package up and distribute your project.
On Tue, 26 Apr 2016 at 05:42 akash chaudhary wrote:
> Hi
>
> I want to distribute my python project that select best proxy and changes
> it to chrome browser o
On Tue, 15 Mar 2016 at 09:42 Chris Barker wrote:
> Probably not the right list but:
>
> There are a number of folks having issue siwth new PyPi pacakges not being
> found by search:
>
>
> https://bitbucket.org/pypa/pypi/issues/412/my-package-doesnt-show-up-in-search
>
> clearly issues have been p
On Thu, 17 Mar 2016 at 17:51 Chris Barker - NOAA Federal <
chris.bar...@noaa.gov> wrote:
>
> b) Is there a serious lack of folks available to address such issues?
>>
>
> This is the correct answer. I can't even keep on top of the request from
> people wanting to take over packages.
>
>
> if (b), s
On Thu, 11 Feb 2016 at 10:01 M.-A. Lemburg wrote:
> On 11.02.2016 17:48, Donald Stufft wrote:
> >
> >> On Feb 11, 2016, at 11:08 AM, M.-A. Lemburg wrote:
> >>
> >> Then why not fix distutils' sdist command to add the needed
> >> information to PKG-INFO and rely on it ?
> >>
> >> Or perhaps add a
Maybe I'm totally overlooking something or misreading the docs, but I can't
find a way to say in a requirements.txt file that a dependency is optional
and its failure to install is okay. E.g., aiohttp supports using cchardet
as an accelerator of chardet (
http://aiohttp.readthedocs.org/en/stable/#l
On Tue, 26 Jan 2016 at 14:36 Nathaniel Smith wrote:
> On Mon, Jan 25, 2016 at 8:37 PM, Robert T. McGibbon
> wrote:
> > I agree that this is an important detail. I generally use machines that
> have
> > many different Python interpreters installed (some distro-provided and
> > others in my home d
On Tue, 26 Jan 2016 at 10:59 Robert T. McGibbon wrote:
> On Mon, Jan 25, 2016 at 1:51 PM, Robert T. McGibbon
> wrote:
>
>>
>> HTML version:
>> https://github.com/manylinux/manylinux/blob/master/pep-513.rst
>>
>
> Nick, at some point would it be possible to put update the version in the
> PEPs re
On Thu, 21 Jan 2016 at 06:48 John Whitlock wrote:
> A discussion about the Python language classifiers came up in a pull
> request [1], and I couldn't find a definite answer. The question is -
> should a packager specify the major Python versions, minor Python versions,
> or both?
>
> The Python
On Wed, 11 Nov 2015 at 04:06 Paul Moore wrote:
> On 11 November 2015 at 06:35, Nick Coghlan wrote:
> > Windows Python 2 installations require manual PATH modifications
> > regardless, but it's more common for people to know how to make
> > "python -m pip install X" work, than it is for them to r
Thanks for writing the roadmap, Marcus! Heck of a lot easier to understand
what is or is not sitting at a PEP at the moment.
On Mon, 2 Nov 2015 at 18:13 Marcus Smith wrote:
> Based on discussions in another thread [1], I've posted a PR to pypa.io
> for a "PyPA Roadmap"
>
> PR: https://github.com
On Thu, 29 Oct 2015 at 22:53 Marcus Smith wrote:
>
>
>> If python-dev ends up adopting GitLab for the main PEPs repo, then we
>> should be able to move the whole process there, rather than needing to
>> maintain a separate copy.
>>
> will that be as open as pypa/interoperability-peps?
>
Proof of
On Thu, 29 Oct 2015 at 12:03 Donald Stufft wrote:
> On October 29, 2015 at 2:54:19 PM, Daniel Holth (dho...@gmail.com) wrote:
> > I think that would be very handy, especially making setuptools not a
> > special case. You could get it down to 3 lines in setup.cfg, a file that
> > already exists an
On Tue, 27 Oct 2015 at 02:17 Robert Collins
wrote:
> On 27 October 2015 at 21:47, David Cournapeau wrote:
>
> > Another simple solution for this particular case is to add conflict rules
> > between packages that provide the same requirement (that's what php's
> > composer do IIRC).
> >
> > The c
On Wed, 21 Oct 2015 at 10:17 Paul Moore wrote:
> On 21 October 2015 at 17:42, Chris Barker wrote:
> > So why not have a setuptools-lite that only does the building? We need to
> > keep the full over-burdened setuptools around, because lot sof folks are
> > using those features. But for those of
Distutils-sig has nothing to do with py2dsc so I doubt anyone can really
help here unfortunately. I would try reaching out to py2dsc or the
flask-login team.
On Wed, 21 Oct 2015 at 13:51 Marques Johansson
wrote:
> I assume I am doing something wrong, but the man page seems a bit light on
> the m
Listening in to an On Air session is unbounded, but direct participants are
capped at 10.
On Fri, 9 Oct 2015 at 09:17 Ionel Cristian Mărieș
wrote:
>
> On Fri, Oct 9, 2015 at 7:05 PM, Chris Barker
> wrote:
>
>> How many people can join a hangout? we may be bumping up against that
>> limit :-)
>
On Sat, 3 Oct 2015 at 04:51 Paul Moore wrote:
> On 3 October 2015 at 02:03, Nathaniel Smith wrote:
> > In particular I hesitate a little bit to just drop in everything from
> > PEP 426 and friends, because previous specs haven't really thought
> > through the distinction between sdists and wheel
On Fri, 2 Oct 2015 at 05:08 Donald Stufft wrote:
> On October 2, 2015 at 12:54:03 AM, Nathaniel Smith (n...@pobox.com) wrote:
> > > We realized that actually as far as we could tell, it wouldn't
> > be that
> > hard at this point to clean up how sdists work so that it would be
> > possible to mig
On Tue, 29 Sep 2015 at 11:34 Mike O'Driscoll
wrote:
> Would someone be able to point me to the correct package/developer bring
> up/testing instructions.
>
> Should I find extra cycles I could potentially investigate a fix.
>
>
I think these might be the instructions you're looking for:
https://w
On Thu, 20 Aug 2015 at 10:16 Wes Turner wrote:
>
> On Aug 20, 2015 5:05 AM, "Nick Coghlan" wrote:
> >
> > [Catching up on distutils-sig after travel]
> >
> > On 13 August 2015 at 16:08, Nathaniel Smith wrote:
> > > It seems like a reasonable effort at solving this problem, and I guess
> > > the
On Wed, Jul 22, 2015 at 9:12 PM Wes Turner wrote:
>
> On Jul 22, 2015 5:12 PM, "Brett Cannon" wrote:
> >
> >
> >
> > On Wed, Jul 22, 2015 at 2:19 PM Wes Turner wrote:
> >>
> >> https://github.com/dstufft/pypi-stats
> >>
>
it's probably worth it to add RDFa to PyPi and warehouse pages (in
> addition to the auxiliary executed/extracted JSON) for #search
> On Jul 22, 2015 4:08 PM, "Brett Cannon" wrote:
>
>> When I wrote https://nothingbutsnark.svbtle.com/python-3-support-on-pypi
>>
When I wrote https://nothingbutsnark.svbtle.com/python-3-support-on-pypi I
wrote a script to download every project's JSON metadata by scraping the
simple index and then making the appropriate GET request for the JSON
metadata. It worked, but somewhat of a hassle.
Is there some dump somewhere that
The way I handled itnin importlib was to version check in setup.py and if
importlib would be in the stdlib I would use an empty list to represent
what to install. That way users didn't have use markers and need to know
importlib was in some specific version of Python (basically argparse has
made pe
I'm traveling so I can't do a thorough reply, but a goal of mine for
Python 3.6 is finally solve the data access problem for packages based on
Donald's importlib.resources proposal as well as pkg_resources to try and
learn from previous mistakes.
On Mon, Jun 29, 2015, 04:52 Paul Moore wrote:
>
On Tue, Apr 14, 2015 at 8:34 PM Ben Finney
wrote:
> Nick Coghlan writes:
>
> > Yep, Guido's keynote was the genesis of the thread.
>
> I can't find it online, can you give a URL so we can see the talk?
>
https://www.youtube.com/watch?v=G-uKNd5TSBw
>
> > Past suggestions for social features ha
On Mon, Apr 13, 2015 at 10:13 PM Donald Stufft wrote:
>
> > On Apr 13, 2015, at 8:57 PM, Ben Finney
> wrote:
> >
> > Nick Coghlan writes:
> >
> >> On 11 Apr 2015 12:22, "Alexander Walters"
> wrote:
> >>> Is the package index really the best place to put this? This is a
> >>> very social-networ
On Mon Feb 09 2015 at 2:42:46 PM Barry Warsaw wrote:
> On Feb 08, 2015, at 11:37 PM, Richard Jones wrote:
>
> >Google has discontinued support for OpenID, so we're not going to be
> >putting any effort into debugging this issue.
>
> I hope you'll continue to support other OpenID providers, e.g. L
On Mon Jan 26 2015 at 1:29:50 PM Jannis Leidel wrote:
>
> > On 25 Jan 2015, at 21:03, Marc Abramowitz wrote:
> >
> > Actually, they do:
> >
> > https://twitter.com/ThePyPA
> >
> > But I don't know if they are in the habit of thinking to use it every
> time something worthy happens.
>
> Currently
On Sat Jul 05 2014 at 9:26:26 AM, Daniel Holth wrote:
> Setuptools supports it even without wheel.
>
How do you specify that since PEP 426 is oriented towards JSON metadata.
Would it be:
test_requires = ["unittest2;python_version < '3.0'"]
?
> On Jul 5, 201
Wheels.
>>
>> Basically you do a conditional include to install_requires in your
>> setup.py, and then if
>> you’re creating wheels you do something like ->
>> https://github.com/dstufft/twine/blob/master/setup.cfg#L9-L13
>>
>> That will overwrite install_
I just checked PEP 440 and pip doesn't seem to have anything specific, so I
thought I would ask if there is any way now or in the future to specify
that a dependency is only needed for certain versions of Python?
My current use case is I want to use unittest2, but pip errors out during
installatio
On 1404130668299, batoot zilzel wrote:
> hi am blind and am python programmer but i can't write the codes from
> python idl should i use notepat ++ and some plugins to write and run
> the codes cause the python idlis not accessible with blind and with
> the screen reader i hope to hear from you
I'm arriving Tuesday night and not leaving until Wednesday morning of the
sprints.
On Fri Mar 28 2014 at 3:07:26 PM, Daniel Holth wrote:
> Who is going to pycon? I will be there.
> ___
> Distutils-SIG maillist - Distutils-SIG@python.org
> https://mai
On Mon Mar 24 2014 at 6:09:48 PM, Barry Warsaw wrote:
> On Mar 24, 2014, at 05:53 PM, Donald Stufft wrote:
>
> >See also https://github.com/pypa/pip/issues/3
>
> Hah, yeah. I didn't realize --single-version-externally-managed is
> implied by
> --root, and in fact our Debian build scripts often (
On Thu Mar 20 2014 at 12:51:13 AM, Nick Coghlan wrote:
> On 20 March 2014 09:54, Vinay Sajip wrote:
> > Daniel Holth gmail.com> writes:
> >
> >> extensions without using distutils. The problem of invoking the
> >> compiler has been solved by many build systems and is not just a
> >> unique and
On Thu, Feb 27, 2014 at 6:49 AM, Piotr Dobrogost <
p...@google-groups-2014.dobrogost.net> wrote:
> Hi!
>
> I've seen people putting 'setuptools' in 'install_requires' in
> setup.py starting with import from setuptools like this:
> from setuptools import setup, find_packages
>
> Does it make any se
docs out
> again :)
>
> On Feb 21, 2014, at 3:32 PM, Brett Cannon wrote:
>
> Well, the docs gave the gpg command to use and made the good point that
> doing so meant not typing your GPG passphrase into a strange app. Anyway,
> https://pypi.python.org/pypi/caniusepython3 is now liv
, Feb 21, 2014 at 3:16 PM, Donald Stufft wrote:
> Twine just uses gpg like distutils upload does. It’ll even do the signing
> for you if you want.
>
> twine upload -s dist/*
>
> On Feb 21, 2014, at 3:02 PM, Brett Cannon wrote:
>
> Well, I'll at least use what twine s
Well, I'll at least use what twine supports. =)
On Fri, Feb 21, 2014 at 2:17 PM, Donald Stufft wrote:
>
> On Feb 21, 2014, at 2:11 PM, Brett Cannon wrote:
>
> So I'm trying to be a good Python project owner for
> https://github.com/brettcannon/caniusepython3 so that m
So I'm trying to be a good Python project owner for
https://github.com/brettcannon/caniusepython3 so that means wanting to
produce a universal wheel. While reading up on exactly what is needed I
noticed there is `wheel keygen` which feeds `wheel sign`.
But what exactly is the keygen producing? I'm
On Sat, Feb 1, 2014 at 3:00 PM, Vinay Sajip wrote:
> On Sat, 1/2/14, Brett Cannon wrote:
>
> > No one is talking about solving this problem overnight.
> > But if we don't want to bother putting the effort in now
> > then the zipimport module might as well get tos
On Sat, Feb 1, 2014 at 2:00 PM, Vinay Sajip wrote:
> On Sat, 1/2/14, Brett Cannon wrote:
>
> > Yes, that is definitely a design flaw in the ssl module that should
> > get remedied. Did you file a bug to add a new API (whether new
> > function or new parameters) to acce
On Sat, Feb 1, 2014 at 1:16 PM, Brett Cannon wrote:
>
>
>
> On Sat, Feb 1, 2014 at 1:00 PM, Paul Moore wrote:
>
>> On 1 February 2014 17:53, Vinay Sajip wrote:
>> >> My pref is [...] and really pushing people to use the loader APIs
>> >> fo
On Sat, Feb 1, 2014 at 1:16 PM, Brett Cannon wrote:
>
>
>
> On Sat, Feb 1, 2014 at 1:00 PM, Paul Moore wrote:
>
>> On 1 February 2014 17:53, Vinay Sajip wrote:
>> >> My pref is [...] and really pushing people to use the loader APIs
>> >> fo
On Sat, Feb 1, 2014 at 1:00 PM, Paul Moore wrote:
> On 1 February 2014 17:53, Vinay Sajip wrote:
> >> My pref is [...] and really pushing people to use the loader APIs
> >> for reading intra-package "files".
> >
> > +1
> >
> >> Maybe the Packaging Users Guide could have a
> >> Recommended Deploy
On Sat, Feb 1, 2014 at 12:34 PM, Donald Stufft wrote:
> On Sat, Feb 1, 2014, at 12:26 PM, Brett Cannon wrote:
>
>
>
>
> On Sat, Feb 1, 2014 at 3:23 AM, Vinay Sajip wrote:
>
>
> On Fri, 31/1/14, Brian Wickman wrote:
>
> > There are myriad other practical rea
On Sat, Feb 1, 2014 at 3:23 AM, Vinay Sajip wrote:
> On Fri, 31/1/14, Brian Wickman wrote:
>
> > There are myriad other practical reasons. Here are some:
>
> Thanks for taking the time to respond with the details - they are good
> data points
> to think about!
>
> > Lastly, there are social rea
On Thu, Jan 30, 2014 at 12:46 PM, Evgeny Sazhin wrote:
> On Thu, Jan 30, 2014 at 11:59 AM, Donald Stufft wrote:
> >
> > On Jan 30, 2014, at 11:33 AM, Evgeny Sazhin wrote:
> >
> >> On Thu, Jan 30, 2014 at 3:09 AM, Paul Moore
> wrote:
> >>> On 30 January 2014 05:33, Evgeny Sazhin wrote:
> >
On Wed, Jan 29, 2014 at 9:40 AM, Donald Stufft wrote:
>
> On Jan 29, 2014, at 9:25 AM, Vinay Sajip wrote:
>
> >> It may be useful to understand that wheel has *political features* or
> >> if you prefer *setting the defaults based on what we have learned from
> >> eggs*. I don't recommend that th
On Thu, Jan 2, 2014 at 11:12 AM, Vinay Sajip wrote:
>
>
> On Thu, 2/1/14, Brett Cannon wrote:
>
> >> "Progamming Language :: Python :: Python2and3"
> >> or some such.
>
> > How is that any better th
On Thu, Jan 2, 2014 at 9:37 AM, Vinay Sajip wrote:
>
>
> On Thu, 2/1/14, Nick Coghlan wrote:
>
> > Dariusz Suchojad suggested it might be easier if there was a
> > suitable classifier to mark such modules rather than trying to keep a
> > list on the w
On Wed, Sep 18, 2013 at 10:26 AM, Nick Coghlan wrote:
> In creating the next draft of PEP 453, I noticed an odd quirk of the
> proposed "pyvenv --no-download" option: it bootstraps the version of
> pip *that was provided with Python*, rather than the version currently
> installed in the base Pyth
On Fri, Aug 30, 2013 at 9:44 AM, Donald Stufft wrote:
> [SNIP]
> Pre-installation
>
>
> During the installation of Python from Python.org ``python -m getpip``
> should
> be executed. Leaving people using the Windows or OSX installers with a
> working
> copy of pip once the instal
On Tue, Aug 20, 2013 at 11:10 AM, Steve Dower wrote:
> Oscar Benjamin wrote:
> > Paul wrote:
> >> Given that the installer includes the py.exe launcher, if you leave the
> >> defaults, then at a command prompt "python" doesn't work. But that's
> fine,
> >> because "py" does. And if you have multip
On Fri, Jul 19, 2013 at 4:31 AM, Nick Coghlan wrote:
> On 19 July 2013 18:17, Paul Moore wrote:
> > On 19 July 2013 05:06, Nick Coghlan wrote:
> >>
> >> * (hopefully) add support for indirect imports (see
> >> http://mail.python.org/pipermail/import-sig/2013-July/000645.html for
> >> the dr
On Thu, Jul 18, 2013 at 8:33 PM, Daniel Holth wrote:
> On Thu, Jul 18, 2013 at 8:15 PM, Donald Stufft wrote:
> >
> > On Jul 18, 2013, at 7:37 PM, Vinay Sajip
> wrote:
> >
> >>> I think the point is that people might be dependent on this
> functionality and
> >>
> >>> changing it out from undern
On Wed, Jul 17, 2013 at 6:12 PM, Nick Coghlan wrote:
>
> On 18 Jul 2013 06:24, "Oscar Benjamin" wrote:
> >
> > On 17 July 2013 17:59, Brett Cannon wrote:
> > >
> > > But it also sounds like that project providing wheel distributions is
&g
On Wed, Jul 17, 2013 at 12:45 PM, Donald Stufft wrote:
>
> On Jul 17, 2013, at 12:39 PM, Brett Cannon wrote:
>
>
>
>
> On Wed, Jul 17, 2013 at 11:46 AM, Daniel Holth wrote:
>
>> On Wed, Jul 17, 2013 at 11:12 AM, Brett Cannon wrote:
>> > I'm going t
On Wed, Jul 17, 2013 at 11:46 AM, Daniel Holth wrote:
> On Wed, Jul 17, 2013 at 11:12 AM, Brett Cannon wrote:
> > I'm going to be pushing an update to one of my projects to PyPI this week
> > and so I figured I could use this opportunity to help with patches to the
> &
I'm going to be pushing an update to one of my projects to PyPI this week
and so I figured I could use this opportunity to help with patches to the
User Guide's packaging tutorial.
But to do that I wanted to ask what the current best practices are.
* Are we even close to suggesting wheels for sou
On Mon, Jul 15, 2013 at 9:39 AM, Paul Moore wrote:
> I'm looking at the possibility of replacing the current setuptools entry
> point based pip executables with Python scripts. The biggest problem is
> that a script "pip.py" shadows the pip package, making "import pip" fail.
>
> I can get round t
On Sun, Jul 14, 2013 at 2:13 AM, Nick Coghlan wrote:
> Based on the recent discussions, I now plan to reject the pip
> bootstrapping-on-first-invocation approach described in PEP 439 in favour
> of a new PEP that proposes:
> [SNIP]
> * ensuring that, for Python 3.4, "python3" and "python3.4" are
On Sun, Jul 14, 2013 at 4:23 AM, Noah Kantrowitz wrote:
>
> On Jul 14, 2013, at 12:35 AM, Nick Coghlan wrote:
>
> > On 14 July 2013 17:13, Donald Stufft wrote:
> > I think it would be reasonable for the pip maintainers to be asked to
> declare a public API (even if that's "None") using the naming
On Sat, Jul 13, 2013 at 11:15 AM, Paul Moore wrote:
> On 13 July 2013 16:03, Donald Stufft wrote:
>
>>
>> > 1. Install to user-packages by default.
>>
>> Do people really want this? I hadn't seen it (other than if pip was
>> installed to user by default). I think it's a bad idea to switch this o
101 - 200 of 228 matches
Mail list logo
