ng with them is the kind
of change that 3.0 made that ended up getting rolled back where it could.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
I think it was a mistake to have Path(…).open to be honest and I think the main
reason it exists is because open(Path(…)) doesn’t work (yet!). You can’t hang
every single thing you might ever want to do to a Path off the path object.
-----
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7
case if you have a singular RichPath object that can represent
both bytes and str (which is what DirEntry does, which I agree makes it harder…
but that’s already the case with DirEntry.path). However that’s not the case if
you have a bRichPath and uRichPath.
-----
Donald Stufft
PGP:
70/#i-can-t-host-my-project-on-pypi-because-of-x-what-should-i-do
.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
ith PyPI that we consult the
PSF board members, particularly the ones who are lawyers. I do recall that the
last time m3-cdecimal came up [1] you (again) brought up issues you had with
PyPI in an inappropriate venue and as far as I know, you never actually used
any
e of
Warehouse, only that *I* won't implement something until after Warehouse. That
often times means that something won't happen until after Warehouse because of
the severe shortage of people with enough time and motivation to work on this
stuff but if someone did step up more things wou
> On May 6, 2016, at 1:11 PM, A.M. Kuchling wrote:
>
> On Thu, May 05, 2016 at 10:31:48PM -0400, Donald Stufft wrote:
>> I don't believe we've ever told someone that something can't happen because
>> of
>> Warehouse, only that *I* won't impl
ing to be built on top of it. In particularly I’d like
to use this in PyPI and pip- but I can’t unless it’s in the standard library.
—
Donald Stufft
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
I recall, I mean it will
use it if OpenSSL is available but otherwise it has internal implementations
too.
—
Donald Stufft
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mai
le either don’t have OpenSSL or don’t have a new enough OpenSSL for those
implementations. Not having the fallback just makes it more difficult for
people to rely on those hash functions.
—
Donald Stufft
___
Python-Dev mailing list
Python-Dev@p
HA3.
It still will be needed for as long as it’s possible to build Python without
OpenSSL.
—
Donald Stufft
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/
> On May 28, 2016, at 5:06 PM, Guido van Rossum wrote:
>
> But you could choose which implementation to use at compile time based
> on the autoconf output, right?
I think we should follow what hashlib already does. If we want to change the
way it works that's fine but these hashes shouldn't be
.
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
-
Donald Stufft
PGP:
artin
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
Let me echo Nick's th
hence ``pip``).
> ========
>
> Regards,
> Nick.
>
> --
> Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message
o reliable story for CA certs.
>
> I'd like to move to "secure by default". The CA cert situation is solved
> on most platforms.
Please Yes, secure by default +1000
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 33
n-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BC
Isn't changing it in 2.7.6 which is already released and then reverting in
2.7.7 worse? Either way 2.7.6 will have this change and be in the wild and
broken for people who depend on it
> On Dec 17, 2013, at 5:54 PM, Benjamin Peterson wrote:
>
> 2013/12/17 Antoine Pitrou :
>> On Tue, 17 Dec 201
e
> if it msiexec still tries to go out to the network. That would confirm
> it is ensurepip that is the issue (although that does seem most likely).
>
> --David
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org
_
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F
hat actually did it. Giving bytes a format method would not have affected
that either way I don’t believe.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message
consistent -- it always produces text in ASCII
> encoding (by default). The same applies to the http module, which IIUC
> adheres to the standard by treating headers as Latin-1.
>
> --
> --Guido van Rossum (python.org/~guido)
> ___________
> Python-Dev mailing list
> Python-Dev@python.
Python 3
> porting target for recalcitrant module authors, sooner than later.
I really hope this can make it in 3.4, needing to wait another 2 years or so
until this is available would be a shame.
-----
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BC
On Jan 13, 2014, at 1:59 AM, Nick Coghlan wrote:
> On 13 January 2014 16:52, Donald Stufft wrote:
>>
>> On Jan 13, 2014, at 12:45 AM, Glenn Linderman wrote:
>>
>> So then the question is whether to proceed with 3.4, delay this feature to
>> 3.5, or to delay
g exceptions then I think you are strange. It makes
> porting really difficult while you are still trying to figure out
> where the bytes/str boundaries are. I am now deeply suspicious of all
> % formatting.
> ___
> Python-Dev mailing
(how could it? :-), nor does
> plain string concatenation using +.
I think disallowing %s is the right thing to do, but I definitely think numbers
and %b should be allowed.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 33
t would give us a large "compatibility surface" in common
> with Python 2.
%s not accepting str is the major thing I’d personally be against. %s taking
numeric
types and bytes would be fine. The main thing i’d be worried about is where the
RHS
may possibly contain something non A
On Jan 13, 2014, at 5:31 PM, Donald Stufft wrote:
> %s not accepting str is the major thing I’d personally be against.
To be more clear
b”%s” % “abc” == No
b”%s” % 123 == Fine
-----
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 D
secure
resource to be educated on the fact that they need to flip some switch to
do what most of them would expect.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
On Jan 22, 2014, at 5:51 AM, M.-A. Lemburg wrote:
> On 22.01.2014 11:30, Donald Stufft wrote:
>> I would like to propose that a backwards incompatible change be made to
>> Python to make
>> verification of hostname and certificate chain the default instead of
>> r
On Jan 22, 2014, at 6:21 AM, Paul Moore wrote:
> On 22 January 2014 10:30, Donald Stufft wrote:
>> Python 3.4 has made great strides in making it easier for applications
>> to simply turn on these settings, however many people are not aware
>> at all that they need t
On Jan 22, 2014, at 6:30 AM, M.-A. Lemburg wrote:
> On 22.01.2014 11:56, Donald Stufft wrote:
>>
>> On Jan 22, 2014, at 5:51 AM, M.-A. Lemburg wrote:
>>
>>> On 22.01.2014 11:30, Donald Stufft wrote:
>>>> I would like to propose that a backwards inco
ure flag for applications
that don’t provide one. I really don’t like the idea of doing that, but
it would be better than not validating by default.
-----
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message
On Jan 22, 2014, at 6:45 AM, Nick Coghlan wrote:
> On 22 January 2014 21:21, Paul Moore wrote:
>> On 22 January 2014 10:30, Donald Stufft wrote:
>>> Python 3.4 has made great strides in making it easier for applications
>>> to simply turn on these settings, howeve
On Jan 22, 2014, at 7:03 AM, Paul Moore wrote:
> On 22 January 2014 11:29, Donald Stufft wrote:
>>> 1. To be "like the browser" we'd need to use the OS certificate store,
>>> which isn't the case on Windows at the moment (managing those
>>>
On Jan 22, 2014, at 6:58 AM, Nick Coghlan wrote:
> On 22 January 2014 21:36, Donald Stufft wrote:
>> On Jan 22, 2014, at 6:30 AM, M.-A. Lemburg wrote:
>>> The change would also disable all services using self-signed
>>> certificates which are very common in inter
e, anecdotal evidence and what not, but
*every* time I bring this up somewhere I get at least one reply that
looks similar to https://twitter.com/ojiidotch/status/425986619879866368
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2
On Jan 22, 2014, at 9:19 AM, Paul Moore wrote:
> On 22 January 2014 13:55, Donald Stufft wrote:
>>
>> As an additional side note, anecdotal evidence and what not, but
>> *every* time I bring this up somewhere I get at least one reply that
>> looks similar to ht
t; about it at one stage. If I *were* to set up an index, it's definitely
> why I'd use http rather than bothering with https.)
>
> Paul
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/p
oo.
Last time I tried the reasoning was that Python couldn’t ship root certs
and we couldn’t get to the OS certs everywhere. Thanks to you this
is fixed now, so “once more unto the breach”.
>
> Can't we just mark these things as pending deprecated in Python 3.4 so
> people start fixi
store that worked on platforms such as
Windows and Python was unwilling to ship it’s own certificate bundle.
Christian has improved this situation so that it appears that this issue has
been largely resolved.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F0
gt; applications I write, but I can careless until it breaks. So as we moving
>> forward, we can break it. For those stuck behind, deprecation is the right
>> approach.
>
> They're disabled by default, so a lot of people simply don't know they
> exist because they a
Never mind. If someone else cares they can propose it. I withdraw.
> On Jan 22, 2014, at 4:29 PM, Brett Cannon wrote:
>
>
>
>
>> On Wed, Jan 22, 2014 at 3:56 PM, Benjamin Peterson
>> wrote:
>>
>>
>> On Wed, Jan 22, 2014, at 12:25 PM, Nick Coghlan wrote:
>> > On 23 Jan 2014 00:39, "Benjam
urity of the network
> remains broken yet there aren't warnings out to avoid these platforms.
> (BTW, my employer prides itself on being Matz's alma mater ... they
> actually might do something if Ruby was breaking things!)
Ruby has verified the peer by default since Ruby
On Jan 23, 2014, at 10:09 PM, Donald Stufft wrote:
>
> On Jan 23, 2014, at 10:06 PM, Stephen J. Turnbull wrote:
>
>> Wes Turner writes:
>>>> But if it's only the already security-conscious developers and
>>>> managers who go WTF?, and other env
man/options/python-dev/donald%40stufft.io
So right now pip doesn’t work without TLS, we’re working on that and our 1.6
release
should have that. I *thought* that Nick (I think?) had made it so that you just
didn’t get pip
if you didn’t have TLS enabled, but apparently not.
You can suppress
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
Does it affect 3.4?
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signa
/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
It is in 3.4.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
ail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
Hash randomization is broken and doesn’t fix anything. It’s only SipHash in
3.4+ that actually fixes it.
-
Donald Stufft
PGP: 0x6E3CBCE93372DC
Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
More information available here: http://legacy.python.org/dev/peps/pep-0456/
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Desc
On Feb 25, 2014, at 8:17 AM, Antoine Pitrou wrote:
> On Tue, 25 Feb 2014 08:08:09 -0500
> Donald Stufft wrote:
>>
>> Hash randomization is broken and doesn’t fix anything.
>
> Not sure what you mean with "doesn't fix anything". Hash collisions were
&
ough. I
*do* believe that calling it fixed is misleading to people who will assume it
means they no longer have to worry about a trivial DoS via hash collisions when
they still do need to, just slightly different than before.
In the end, it’s good that it was fixed in 3.4, I wish it had been back
some extra cleaning at the 4.0
>> boundary, just for mental convenience.)
>>
> What does "irregardless" mean?
http://www.merriam-webster.com/dictionary/irregardless
> ___
> Python-Dev mailing l
ail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
AFAIK the www.python.org PEP stuff just isn’t done yet, and the legacy redirect
is
a temporary stopgap.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7
___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B
I think the pep doesn't mandate that someone does. It still requires someone to
care enough to actually write the patch. It just allows such a patch to be
merged.
> On Mar 22, 2014, at 5:32 PM, Benjamin Peterson wrote:
>
> Does anyone really want to backport features to Python 3.1?
__
"Just use Python 3.4" ignores the reality of production software. I wish it
were that simple because I love 3.4
> On Mar 22, 2014, at 6:16 PM, "Martin v. Löwis" wrote:
>
> Am 22.03.14 22:17, schrieb Cory Benfield:
>> I am 100%, overwhelmingly in favour of this. Without this PEP, Python 2.7
>> i
those situations affect more people than just the developers and users of
>> the affected application: their existence becomes something that developers
>> of secure networked services need to take into account as part of their
>> security design. By making it more feasible to enh
In the case of requests they already have an optional dependency on pyopenssl.
It's just many people either don't know they should use it, are unable to use
it, or unwilling to use the python packaging tool chain because of its current
flaws.
> On Mar 22, 2014, at 7:42 PM, Ben Darnell wrote:
Also important to remember that pip itself uses the OpenSSL binding in the ssl
module so there is a chicken and egg problem.
> On Mar 22, 2014, at 7:49 PM, Donald Stufft wrote:
>
> In the case of requests they already have an optional dependency on
> pyopenssl. It's just m
They detect for ssl to have the SSLContext and use it if it's available.
> On Mar 22, 2014, at 7:54 PM, Paul Moore wrote:
>
>> On 22 March 2014 23:49, Donald Stufft wrote:
>> In the case of requests they already have an optional dependency on
>> pyopenssl. It&#x
ib. CPython isn’t our only target and C dependencies don’t work very
well on PyPy (if at all) and it makes the situation much more difficult on
platforms where there are no compiler toolchains (Windows).
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A92
if it
requires any work at
all. Going from 2.7 to 3.4 is often times a significant investment in resources
that has
to be taken by *every* network using project.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Descript
mail.com | Brisbane, Australia
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/brett%40python.org
ed OpenSSL module?
>
> * Are there any other security relevant modules that should be covered
> by either a blanket or conditional exemption?
>
>
> Disclosure of Interest
> ==
>
> The author of this PEP cu
thon.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
I already did open an issue and write a patch :)
There’s someone on that issue saying that flipping that without a way to flip
it back
would brea
On Mar 23, 2014, at 11:46 AM, Antoine Pitrou wrote:
> On Sun, 23 Mar 2014 11:37:25 -0400
> Donald Stufft wrote:
>>
>> I already did open an issue and write a patch :)
>>
>> There’s someone on that issue saying that flipping that without a way to
>&g
-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message si
On Mar 23, 2014, at 11:55 AM, Mark Lawrence wrote:
> On 23/03/2014 15:46, Antoine Pitrou wrote:
>> On Sun, 23 Mar 2014 11:37:25 -0400
>> Donald Stufft wrote:
>>>
>>> I already did open an issue and write a patch :)
>>>
>>> There’s someone on
stinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
/mailman/options/python-dev/donald%40stufft.io
I agree, the bulk of the alternative suggestions feel more like trying to
adhere to a policy for policy’s sake rather than actually figure out what is
best for the users.
Adding new APIs to 2.7 feels to me like a pretty backwards compat
ython.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Descrip
ent of
influential members who still want to treat Python as a hobbyist project and
not a critical piece of the infrastructure of the Internet as a whole. I
*don't* want to get help from downstream users, especially on important but
"boring" or hard issues such as security, and then have
he sense that APIs can’t change
their default behavior and such. In other words we can’t suddenly flip on
hostname checking or anything like that.
>
> --
> --Guido van Rossum (python.org/~guido)
> ___
> Python-Dev mailing list
> Pyth
On Mar 25, 2014, at 1:16 PM, Guido van Rossum wrote:
> On Tue, Mar 25, 2014 at 9:46 AM, Donald Stufft wrote:
>
> On Mar 25, 2014, at 12:35 PM, Guido van Rossum wrote:
> [...]
>>
>> I do note that the PEP seems to have some weasel-words about breaking
>> back
> > Unsubscribe:
> > https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.or
n,
> and has thus been replaced by the current more explicit proposal.
>
>
> Open Questions
> ==
>
> * MvL has indicated he is not prepared to tackle the task of trying to
> integrate a newer OpenSSL into the also aging Python 2.7 build
> infrastructu
ormational
> Content-Type: text/x-rst
> Created: 23-Mar-2014
> Post-History: 23-Mar-2014, 24-Mar-2014, 25-Mar-2014, 26-Mar-2014
>
>
This looks reasonable to me still and still solves the major problems that
trying to securely
use the 2.7 series has.
+1 From me.
--
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
Is that what it’s called? “character” >:]
-
Donald Stufft
P
on.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
Probably infrastructure-st...@python.org
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372
On Apr 9, 2014, at 10:30 PM, Senthil Kumaran wrote:
> Mentioned about https://pypi-preview.a.ssl.fastly.net/
For what it’s worth, https://warehouse.python.org/ is a somewhat easier to
remember demo url for that :]
-----
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5
ying a core developer full time, but
>> it's the starting point that some companies will need to be able to
>> become comfortable with employing a core dev.
>
> Let's hope some act on your invitation.
>
> --
> Terry Jan Reedy
>
> __
On Apr 14, 2014, at 4:39 PM, Guido van Rossum wrote:
> On Mon, Apr 14, 2014 at 4:02 PM, Donald Stufft wrote:
>
> On Apr 14, 2014, at 3:53 PM, Terry Reedy wrote:
>
> > On 4/14/2014 11:32 AM, Steve Dower wrote:
> [...]
> >> However unfair
> >> and incorr
on.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
Possibly Glyph meant installing a Python *stack*, which likely includes
setuptools and
pip in order to actually get other things installable. Possibly also a compiler
set
s not all startup related, often comes as an additional slap in the face. :-(
>
> Best regards,
>Jurko Gospodnetić
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/pyt
_
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
Fastly logs are stored in Dreamhost so we could make those num
lop something to make it easier
like a build farm).
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Python-Dev ma
On Apr 18, 2014, at 4:22 PM, Nick Coghlan wrote:
> On 18 April 2014 15:39, Donald Stufft wrote:
>>
>> On Apr 18, 2014, at 3:18 PM, Nick Coghlan wrote:
>>
>>> At this point, however, I'm mainly looking for consensus that there
>>> *are* two diffe
On Apr 18, 2014, at 4:50 PM, Donald Stufft wrote:
> So I’m not really worried about a competition or anything. I’m mostly worried
> about confusion of users. What you’re suggestion we give to use is *two* ways
> to install Python packages (and 2 or 3 ways to virtualize a Python
On Apr 18, 2014, at 5:08 PM, Nick Coghlan wrote:
> On 18 April 2014 16:50, Donald Stufft wrote:
>> So I’m not really worried about a competition or anything. I’m mostly worried
>> about confusion of users. What you’re suggestion we give to use is *two* ways
>> to install P
). And the 1.x
> versions were just as simple.
>
> Paul
Maybe Nick meant ``pip install ipython[all]`` but I don’t actually know what
that
includes. I’ve never used ipython except for the console.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E
On Apr 18, 2014, at 6:24 PM, Nick Coghlan wrote:
> On 18 April 2014 18:17, Paul Moore wrote:
>> On 18 April 2014 22:57, Donald Stufft wrote:
>>> Maybe Nick meant ``pip install ipython[all]`` but I don’t actually know
>>> what that
>>> includes. I’ve never
On Apr 18, 2014, at 6:37 PM, Nick Coghlan wrote:
> On 18 April 2014 18:28, Donald Stufft wrote:
>>
>> On Apr 18, 2014, at 6:24 PM, Nick Coghlan wrote:
>>
>>> On 18 April 2014 18:17, Paul Moore wrote:
>>>> On 18 April 2014 22:57, Donald Stufft w
going to be 3.5+
anyways. It seems like trying to fit as many of these compatibility things as
Python is willing to do into 3.5 is the best possible solution since it’s
likely that for a lot of these hanger-ons 3.5 is likely to be a minimum target
anyways.
---------
Donald Stufft
PGP: 0x
n the side of being too
> strict with PEP 8's recommendations than too loose. Again, it's not hard
> to turn off the ones you don't want.
>
> If python-dev wants to control the precise behavior of pep8.py, bring it
> into the standard libr
t against it.
>
> Sincerely,
>
> --
> Florent
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stuf
On Apr 25, 2014, at 7:20 PM, Ethan Furman wrote:
> On 04/25/2014 03:26 PM, Donald Stufft wrote:
>>
>> pep8.py doesn’t violate PEP8, it just takes a stricter view of it.
>
> If pep8 reports errors on things that PEP 8 says are okay, that's a v
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io
-
> After all, people might be led to believe that pip is some sort of apt-get
> and all uploaded packages are safe.
>
>
> Stefan Krah
>
>
>
> [1] Note that the joke is quite innocent in comparison to what I've read on
>distutils-sig about the subject.
>
>
was, typically unknown to them,
hosted externally and they found out it was hosted externally because the
server it was hosted on went down.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Mes
201 - 300 of 497 matches
Mail list logo
