David Beazley added the comment:
Just as a note, there is a distinct possibility that a "property" in a
superclass could be some other kind of descriptor object that's not a property.
To handle that case, the solution of
super(self.__class__, self.__class__).x.fset(self
New submission from David Beazley:
Suppose you subclass a dictionary:
class mdict(dict):
def __getitem__(self, index):
print('Getting:', index)
return super().__getitem__(index)
Now, suppose you define a function and perform these steps that reassign the
David Beazley added the comment:
I have run into this bug myself. Agree that a file-like object should never
report itself as closed unless .close() has been explicitly called on it.
HTTPResponse should not return itself as closed after the end-of-file has been
reached.
I think there is
David Beazley added the comment:
There are other kinds of libraries that might want to access the .buf
attribute. For example, the llvmpy extension. Exposing it would be useful.
--
___
Python tracker
<http://bugs.python.org/issue15
David Beazley added the comment:
Well, a lot of things in this big bad world are dangerous. Don't see how this
is any more dangerous than all of the peril that tools like ctypes and llvmpy
already provide.
--
___
Python tracker
David Beazley added the comment:
One of the other goals of memoryviews is to make memory access less hacky. To
that end, it would be nice to have the .buf attribute available given that all
of the other attributes are already there. I don't see why people should need
to do some even
New submission from David Beazley:
Not so much a bug, but an observation based on reviewing the implementation of
the selectors.KqueueSelector class. In that class there is the select() method:
def select(self, timeout=None):
timeout = None if timeout is None else max
David Beazley added the comment:
If the KQ_FILTER constants aren't bitmasks, it seems that the code could be
simplified to the last version then. At the least, it would remove a few
unnecessary calculations.Again, a very minor thing (I only stumbled onto it
by accident r
David Beazley added the comment:
I don't see any possible way that you would ever get events = EVENT_READ |
EVENT_WRITE if the flag is a single value (e.g., KQ_FILTER_READ) and the flag
itself is not a bitmask. Only one of those == tests will ever be True. There
is no need t
David Beazley added the comment:
This is a problem that will never be fixed. Sure, it was a release blocker in
Python 3.4.
It wasn't fixed.
It is a release blocker in Python 3.5.
It won't be fixed.
They'll just tell you to indent using the spacebar as generations of typists
David Beazley added the comment:
For what it's worth, I'm kind of tired having to hack site.py every time I
upgrade Python in order to avoid being shown 6000 choices when hitting tab on
an empty line. It is crazy annoying.
--
___
Pyth
David Beazley added the comment:
Frivolity aside, I really wish this issue would get more traction and a fix.
Indentation is an important part of the Python language (obviously). A pretty
standard way to indent is to hit "tab" in whatever environment you're using to
edit Py
David Beazley added the comment:
Wanted to add: I see this as being about the same as having a broken window
pane on the front of Python 3. Maybe there are awesome things inside, but it
makes a bad first impression on anyone who dares to use the interactive console
David Beazley added the comment:
It's still broken on Python 3.5b4.
--
___
Python tracker
<http://bugs.python.org/issue23441>
___
___
Python-bugs-list m
New submission from David Beazley:
Just a note that Python-3.5.0rc1 fails to compile on Mac OS X 10.8.5 with the
following compiler:
bash$ clang --version
Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn)
Target: x86_64-apple-darwin12.6.0
Thread model: posix
bash$
Here is the
New submission from David Beazley:
The compile() function is not able to compile an AST created from code that
uses some of the new unpacking generalizations in PEP 448. Example:
code = '''
a = { 'x'
David Beazley added the comment:
This bug is still present in Python 3.5, but it occurs if you attempt to do a
readline() on a socket that's in non-blocking mode. In that case, you probably
DO want to retry at a later time (unlike the timeout
New submission from David Beazley:
First comment: In the I/O library, there is documented behavior for how things
work in the presence of non-blocking I/O. For example, read/write methods
returning None on raw file objects. Methods on BufferedIO instances raise a
BlockingIOError for
David Beazley added the comment:
Please don't make flush() close the file on a BlockingIOError. That would be
an unfortunate mistake and make it impossible to implement non-blocking I/O
correctly with buffered I/O.
--
___
Python tracker
New submission from David Beazley:
I have been investigating some of the new importlib machinery and the addition
of ModuleSpec objects. I am a little curious about the intended handling of C
Extension modules going forward.
Backing up for a moment, consider a pure Python module. It seems
David Beazley added the comment:
inal comment. It seems that one can generally avoid a lot of nastiness if
importlib.reload() is used instead. For example:
>>> mod = sys.modules[spec.name] = module_from_spec(spec)
>>> importlib.reload(mod)
This works for both source and
David Beazley added the comment:
Sorry. I take back the previous message. It still doesn't quite do what I
want. Anyways, any insight or thoughts about this would be appreciated ;-).
--
___
Python tracker
<http://bugs.python.org/is
David Beazley added the comment:
Note: Might be related to Issue 19713.
--
___
Python tracker
<http://bugs.python.org/issue23642>
___
___
Python-bugs-list mailin
David Beazley added the comment:
This is great news. Read the PEP draft and think this is a very good thing to
be addressing. Thanks, Brett.
--
___
Python tracker
<http://bugs.python.org/issue23
101 - 124 of 124 matches
Mail list logo
