Glyph Lefkowitz added the comment:
This has been a serious annoyance in the Twisted and pyOpenSSL release
processes; it effectively prevents us from timely uploads of win32 binaries of
any kind.
--
nosy: +glyph
___
Python tracker
<h
Glyph Lefkowitz added the comment:
Would it be possible to have this reverted for 2.7.2 / 3.2.1, and restore
~/.local _and_ ~/Library as equally valid locations for python code?
As I tried to explain on the mailing list, this change basically introduces a
regression, and nothing else. Sorry
Glyph Lefkowitz added the comment:
I agree with Michael Foord; my comment on issue 8404
<http://bugs.python.org/issue8084#msg122935> may be of interest to anyone
looking at this as well.
--
___
Python tracker
<http://bugs.python.org/
Glyph Lefkowitz added the comment:
I would still prefer
~/.local/something-parallel-to-where-it's-usually-installed for its ease of
documentation. But ~/.python/X.Y isn't terribly objectionable.
A minor point about Michael Foord's fallback proposal: I don't know why
ev
Glyph Lefkowitz <[EMAIL PROTECTED]> added the comment:
As barry said, this should have been a release blocker for the first
beta... ;-)
--
nosy: +glyph
priority: critical -> release blocker
___
Python tracker <[EMAIL PROTE
Glyph Lefkowitz <[EMAIL PROTECTED]> added the comment:
Looks like we just misunderstood the way the warnings filter works, and
catch_warnings' interaction with it. Thanks for the priority bump,
guido, and sorry for the false alarm!
--
nosy: +glyph
status: ope
Changes by Glyph Lefkowitz <[EMAIL PROTECTED]>:
--
resolution: -> invalid
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3780>
___
__
Glyph Lefkowitz <[EMAIL PROTECTED]> added the comment:
The use of the term "filter" is pretty confusing. I would normally say
it was just me, but a bunch of other Twisted hackers seemed to interpret
it the same way: a "filter" is something that has an opportunity to
r
New submission from Glyph Lefkowitz <[EMAIL PROTECTED]>:
Currently if you have both Python 3 and Python 2 installed, there's no
way to indicate that ".py" files in one area are Python 2 syntax and in
another area are Python 3 syntax. Being able to distinguish between
th
Glyph Lefkowitz <[EMAIL PROTECTED]> added the comment:
I don't understand your objection. It sounds like you're objecting, but
then suggesting an implementation? The line you suggest might just as
easily be present in py3k's default site.py and it would work fine.
As I
Glyph Lefkowitz <[EMAIL PROTECTED]> added the comment:
The idea is that PYTHON3PATH will be honored in preference to
PYTHONPATH, but PYTHONPATH will still be honored. It's exposed only to
people who specifically need it.
However, I think it's misleading to call the Pytho
Glyph Lefkowitz <[EMAIL PROTECTED]> added the comment:
pitrou: You're missing a few steps. If you are maintaining project X,
which depends on library Y, that adds a showwarning hook for some
reason, you need to:
* check out a development version of library Y, which you do n
New submission from Glyph Lefkowitz :
Consider the following example that attempts to make a series of types sortable
by their class name:
from functools import total_ordering
@total_ordering
class SortableMeta(type):
def __new__(cls, name, bases, ns):
return super().__new__
Glyph Lefkowitz added the comment:
Adding versions after confirming the bug is the same on 3.10
--
versions: +Python 3.10, Python 3.11
___
Python tracker
<https://bugs.python.org/issue44
Glyph Lefkowitz added the comment:
> Do you all have preference for 1) expanding the range of use cases to cover
> metaclasses but incurring a performance hit for common cases, or 2) leaving
> it as-is and documenting that it doesn't work for metaclasses?
If we do need the slo
Glyph Lefkowitz added the comment:
> We could do that and not incur performance issues. However, it would expand
> the API and double the size of the code.
If the preference is to not support this use-case, then I'd rather the
decorator simply raise an exception and tell me th
Glyph Lefkowitz added the comment:
My preference would be to fix it one way or another; the stdlib should be
correct before it's performant. If, as you say, it's better to write the
methods longhand anyway for ease of debugging, then it makes sense to write
them out for perfor
Glyph Lefkowitz added the comment:
I hope nobody will mind if I close: It's a duplicate of issue1257 so future
discussion, if any, should probably happen there.
--
nosy: +glyph
resolution: -> duplicate
stage: -> resolved
status: ope
Glyph Lefkowitz added the comment:
This bug has been filed several times:
issue1257
issue11654
and it's tempting to simply close this as a dup, but this ticket mentions the
documentation, which is slightly confusing:
https://docs.python.org/3.8/library/atexit.html#atexit.register
Glyph Lefkowitz added the comment:
gwk, I absolutely agree; at this point that's the main thing I'm looking for.
But it would be great if whoever adds that documentation could include the
rationale for this behavior too. It still seems "obvious" to me that it should
Glyph Lefkowitz added the comment:
I also just discovered this. I thought it must have regressed at some point
but I see the docs say "new in 3.8" and I'm using 3.8.
Is there a "no CI for examples in the docs" issue that this could be linked to?
New submission from Glyph Lefkowitz :
This example:
from __future__ import annotations
from functools import singledispatchmethod
class Comparable:
@singledispatchmethod
def compare(self, arg: object):
raise NotImplementedError("what")
@compare.register
Glyph Lefkowitz added the comment:
The behavior is the same with a traditional quoted forward declaration, so it’s
not specific to the __future__ import; I just phrased the example that way to
show how it’s going to look in the future and to illustrate how it might crop
up in a way which is
Glyph Lefkowitz added the comment:
For what it's worth, I've long since adapted to the status quo here, so I'm
happy for this to just be closed :-).
(Apple seems to have mostly given up on "domains" as a user-facing or even
developer-facing concept, so searching
Glyph Lefkowitz added the comment:
Charles-François:
> Also, I must admit I'm quite skeptical about the real benefit of
explicit probes for user-land, especially for CPython which isn't used
for performance-critical systems...
I beg to differ. CPython is totally used on perform
Changes by Glyph Lefkowitz :
--
nosy: +glyph
status: pending -> open
___
Python tracker
<http://bugs.python.org/issue30392>
___
___
Python-bugs-list mai
Changes by Glyph Lefkowitz :
--
status: open -> pending
___
Python tracker
<http://bugs.python.org/issue30392>
___
___
Python-bugs-list mailing list
Unsubscrib
Glyph Lefkowitz added the comment:
I just bumped into this myself. If this really is only fixable in a major
release, there ought to at least be a minor release for the *documentation* to
update it to be correct.
--
nosy: +glyph
___
Python tracker
Glyph Lefkowitz added the comment:
For what it's worth, it would still be great if this could be merged. It could
help a lot with 2/3 migrations of async code that uses Twisted and wants to
adopt some asyncio parts. Right now the stdlib SSL module is de-facto useless
in those scenario
Glyph Lefkowitz added the comment:
It would be nice for this to be fixed in a 2.7.x release too, if possible,
since the workaround involves a ton of extra system calls and there's no other
way to construct a socket object directly.
--
nosy: +glyph
versions: +Pytho
Glyph Lefkowitz added the comment:
It's worth noting that the "buffer()" built-in in Python2 had this behavior,
and it enabled a copy-reduction optimization within Twisted's outgoing
transport buffer.
There are of course other ways to do this, but it seems like it would
Glyph Lefkowitz added the comment:
Le Oct 11, 2012 à 12:13 PM, Antoine Pitrou a écrit :
>
> Antoine Pitrou added the comment:
>
> I'm not sure what you're talking about since:
>
>>>> b = buffer("abc")
>>>> b + "xyz"
&
Glyph Lefkowitz added the comment:
Yes, it would be *possible* to fix it with that alone, but that still makes it
a pointless 'gotcha' in differing behavior between memoryview and buffer,
especially given that bytes+memoryview does something semantically different
than memoryview+by
Glyph Lefkowitz added the comment:
Just my 2¢ here: rather than debating cases in the abstract, it would be
interesting to 'pip install' a couple of popular 2.x-only packages and see if
the error message is an improvement.
My experience is that learners don't hit this so much b
Changes by Glyph Lefkowitz :
--
nosy: +glyph
___
Python tracker
<http://bugs.python.org/issue12411>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Glyph Lefkowitz :
--
nosy: +glyph
___
Python tracker
<http://bugs.python.org/issue3982>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Glyph Lefkowitz :
--
nosy: +glyph
___
Python tracker
<http://bugs.python.org/issue15958>
___
___
Python-bugs-list mailing list
Unsubscribe:
Glyph Lefkowitz added the comment:
On Jan 22, 2013, at 11:39 AM, Antoine Pitrou wrote:
> Antoine Pitrou added the comment:
>
> I agree with the idea that the feature set should very limited, actually
> perhaps more limited than what you just said. For example, I think any kind
&
Glyph Lefkowitz added the comment:
On Jan 22, 2013, at 1:46 PM, STINNER Victor wrote:
> 2013/1/22 Guido van Rossum :
>> Twisted still would like to see this.
>
> Sorry, but this argument doesn't convince me. A better argument is
> that bytes+bytes+...+bytes is inefficie
Glyph Lefkowitz added the comment:
> Antoine Pitrou added the comment:
> The fact that "there are plenty of other Python applications that don't
> use Twisted which nevertheless need to emit formatted sequences of
> bytes" is *precisely* a good reason for this to be d
Glyph Lefkowitz added the comment:
On Jan 22, 2013, at 3:34 PM, Terry J. Reedy wrote:
> I presume this would mean adding 'if py3: out = out.encode()' after the
> formatting. As I said before, this works much better in 3.3+ than in 3.2-.
> Some actual numbers:
I'm
Glyph Lefkowitz added the comment:
On Jan 22, 2013, at 11:27 PM, Antoine Pitrou wrote:
> Antoine Pitrou added the comment:
>
> The "ASCII superset commands" part is clearly separated from the "binary
> data" part. Your own LineReceiver is able to switch bet
Glyph Lefkowitz added the comment:
On Jan 22, 2013, at 11:31 PM, Martin v. Löwis wrote:
> I admit that it is puzzling that string interpolation is apparently the
> fastest way to assemble byte strings. It involves parsing the format string,
> so it ought to be slower than anyt
Glyph Lefkowitz added the comment:
On Jan 23, 2013, at 1:58 AM, Antoine Pitrou wrote:
> Numbers currently don't have a __bytes__ method:
>
>>>> (5).__bytes__()
> Traceback (most recent call last):
> File "", line 1, in
> AttributeError: 'in
Glyph Lefkowitz added the comment:
On Jan 23, 2013, at 11:02 AM, Antoine Pitrou wrote:
> I would agree with you, but it's probably too late to change...
Understandable, and, in any case, out of scope for this ticket.
--
___
Python tracke
Glyph Lefkowitz added the comment:
On Oct 8, 2013, at 8:10 AM, Augie Fackler wrote:
> Hah. Probably too slow for anything beyond a proof of concept, no?
It should perform acceptably on PyPy ;-).
--
___
Python tracker
<http://bugs.pyth
Glyph Lefkowitz added the comment:
On Oct 8, 2013, at 2:35 PM, Eric V. Smith wrote:
> What proposal is actually on the table here?
Sorry Eric, you're right, there is too much discussion here. This issue ought
to be about .format, like the title says. There should be a separate tic
Glyph Lefkowitz added the comment:
On Oct 8, 2013, at 3:19 PM, Augie Fackler wrote:
> No, I'm not. In Mercurial, all end-user data is OPAQUE BYTES, and must remain
> that way.
The PEP 383 technique for handling file names is completely capable of
round-tripping exact bytes
Glyph Lefkowitz added the comment:
Tempting as it is to reply to the comment about 'buffer' not existing, we're
way off topic here. Let's please keep further comments on this bug to issues
about a 'format'
Glyph Lefkowitz added the comment:
I don't have a whole lot to add. I strongly recommended that this be done this
way twice, once when ssl was added to Python and once when ssl was added to
tulip, so I'm glad to see it's happening now. Regarding the specific
implementation I
Changes by Glyph Lefkowitz :
--
nosy: -glyph
___
Python tracker
<http://bugs.python.org/issue21965>
___
___
Python-bugs-list mailing list
Unsubscribe:
Glyph Lefkowitz added the comment:
Would simply replacing this function with pipes.quote resolve the issue?
--
nosy: +glyph
___
Python tracker
<http://bugs.python.org/issue22
Changes by Glyph Lefkowitz :
--
nosy: +glyph
___
Python tracker
<http://bugs.python.org/issue4111>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Glyph Lefkowitz :
c.f. this Twisted ticket: http://twistedmatrix.com/trac/ticket/3703
Twisted's test tool has an extended TestCase which uses the 'skip'
attribute, on both tests and methods, to determine whether to skip them.
You can see the implementat
Glyph Lefkowitz added the comment:
I went to the trouble of tracking it down and then I forgot to attach a
comment: I'm pretty sure Benjamin meant r70616.
--
___
Python tracker
<http://bugs.python.org/i
Changes by Glyph Lefkowitz :
--
nosy: +glyph
___
Python tracker
<http://bugs.python.org/issue5753>
___
___
Python-bugs-list mailing list
Unsubscribe:
Glyph Lefkowitz added the comment:
Antoine,
The problem is that apparently every program that embeds Python calls
PySys_SetArgv and does not understand the consequences of doing so. For
example, a user running 'gedit' to edit some files in a potentially
insecure directory may not e
Glyph Lefkowitz added the comment:
It suggests to me that somewhere there's some documentation, or an
example, that says "this is the right way to embed python, call this
function".
If the right thing to do is to just not call the function at all, we
need to get that knowledge
Glyph Lefkowitz added the comment:
> IOW, I *really* want to understand what's happening before fixing
> it. This is a security issue, after all.
Agreed. Does anyone currently subscribed to this ticket know the author
of such an application? It would be very helpful to have them
Glyph Lefkowitz added the comment:
> Well, that makes it the user-specific equivalent of /usr or /usr/local.
> Do you put your configuration files in /usr/local ? Why put them
> in .local ?
Yes, software built for /usr/local will often respect /usr/local/etc in
addition to /etc.
A
Glyph Lefkowitz added the comment:
Is the fact that 'await' produces a syntax error in this context the same bug
or a new one?
--
nosy: +glyph
___
Python tracker
<http://bugs.python.o
Glyph Lefkowitz added the comment:
>>> async def foo():
... bar = [await x for x in range(10)]
File "", line 2
SyntaxError: 'await' expressions in comprehensions are not supported
--
___
Python tracker
<h
Glyph Lefkowitz added the comment:
OK, cool. So, long term, there will be a way to do this (suspend within a
generator expression). Thanks for the pointer.
--
___
Python tracker
<http://bugs.python.org/issue10
Glyph Lefkowitz added the comment:
(As far as awaiting on int, yes, I know how await works, I was focusing on the
syntax.)
--
___
Python tracker
<http://bugs.python.org/issue10
New submission from Glyph Lefkowitz:
The purpose of 'seeding' a random number generator is usually to supply a
deterministic sequence of values starting from a known point. This works fine
if you seed random.Random with an integer. Often (for example, see Minecraft's
Glyph Lefkowitz added the comment:
It does seem to be stable on python 3, but on python 2.7 it's definitely a
problem:
$ python -Rc "import random; r=random.Random('abc'); print(''.join(map(str,
(r.randrange(10) for x in range(10, hash('abc'
Glyph Lefkowitz added the comment:
Changing the affected version to just 2.7.
--
versions: -Python 3.5, Python 3.6
___
Python tracker
<http://bugs.python.org/issue27
Glyph Lefkowitz added the comment:
For what it's worth, I don't much care whether this is fixed or not; I ended up
wanting to leak less information from the RNG output anyway so I wrote this:
https://gist.github.com/glyph/ceca96100a3049fefea6f2035abbd9ea
but I felt like it should b
New submission from Glyph Lefkowitz:
As reported in Twisted:
https://twistedmatrix.com/trac/ticket/6314
and as seen on the Twisted buildbot:
https://buildbot.twistedmatrix.com/builders/lucid32-py2.7maint/builds/2327/steps/trial/logs/problems
The tip of the 2.7 branch is now failing Twisted&#
Glyph Lefkowitz added the comment:
Yes; perhaps that change should be rolled back until a fix for the regression
can be added?
--
___
Python tracker
<http://bugs.python.org/issue17
Glyph Lefkowitz added the comment:
Confirmed. Thanks very much for addressing it promptly.
--
resolution: -> duplicate
status: pending -> closed
___
Python tracker
<http://bugs.python.org/i
Glyph Lefkowitz added the comment:
Hi Ned,
It seems from your comment that you didn't read the patch. Alex added a
simpler check via launchctl, rather than by framework symbol groveling :). He
didn't remove the check.
It should be functionally identical to what's ther
Glyph Lefkowitz added the comment:
> Wouldn't it be better to check for the actual problem, that is use subprocess
> to start a small Tcl script that creates a window and check if that crashes?
Yes, this sounds great. Doing it with Tcl means that we're not invoking any of
Glyph Lefkowitz added the comment:
XDG_CONFIG_HOME is not generally set to anything; the default of ~/.config is
usually fine. However, the point is that you _can_ set it to point at a
different location. The relevant specification is here:
http://standards.freedesktop.org/basedir-spec
74 matches
Mail list logo
