R. David Murray added the comment:
Thanks for wanting to work on this.
It is a little hard to parse from the OP's initial post, but he is asking that
%V and %u be supported by datetime.strptime, which they currently are not.
strptime is the generalized constructor for turning a string
R. David Murray added the comment:
You are using the only version that has the bug (3.2.0, also called 3.2). The
fixed version will be released shortly (3.2.1).
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue11
R. David Murray added the comment:
And it goes on to say:
"[...] but a syslog application MAY modify these characters upon reception.
For example, it might change them into an escape sequence (e.g., value 0 may be
changed to "\0")"
Flume should not break if it recei
R. David Murray added the comment:
I'm not familiar with this module, so at the moment I just gave the patch a
quick scan. The approach looks OK to me. Hopefully Alexander can review it.
In the meantime I think you should go ahead and work on tests and doc. It is
easier to do a det
R. David Murray added the comment:
It looks like strftime already support %V and %u (presumably if and only if the
platform strftime does).
--
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
Since this is a new feature it can only go into 3.3.
Documentation is in the Doc subdirectory of a checkout, and is in the form of
*.rst files. Modify the appropriate .rst file, and the doc update will be
included in the patch you generate. If you wish to
R. David Murray added the comment:
I would remove the docstring from the new test class...if more tests of message
content are added that docstring won't be accurate. It really isn't needed.
(Also, shouldn't the test method be named test_missingarguments?)
I would also lik
R. David Murray added the comment:
What is not-a-charset?
I apparently misunderstood what normalize_encodings does. It isn't doing a
lookup in the codecs registry and returning the canonical name for the codec.
Does that mean we actually have to fetch the codec in order to ge
R. David Murray added the comment:
Well, my thought was to avoid having multiple charset alias lists in the
stdlib, and reusing the one in codecs, which is larger than the one in email,
seemed to make sense. This came up because a bug was reported where email
(silently) failed to encode a
R. David Murray added the comment:
There are a number of issues with compile that have been fixed. See #4628 and
#1479099 for example.
Since you say it works with 2.7, and Python3 compile handles \r\n, and 2.6 is
in security fix only mode, I'm closing this as out of date. If you
R. David Murray added the comment:
I agree that since we get very few requests to add aliases our current tables
are probably what we want. So adding the MIME_preferred_name mapping
*somewhere* is indeed what I would like to see happen. It doesn't matter to me
whether it is in the c
R. David Murray added the comment:
Sometimes only one patch is needed, if it applies cleanly to both python2 and
python3. If it doesn't, then two patches are useful, one for python2.7 and one
for python3.2. (The last version of 3.1 is about to be released, so I don't
think it l
R. David Murray added the comment:
Your new file isn't in the patch. I'm imagining it is a table and a couple
methods, so I think perhaps putting it either in charset or in utils would be
better than creating a new file.
As for testing it, what I'd love to see is a test tha
R. David Murray added the comment:
Prompted on IRC, I see I missed the file because it was so short.
This still isn't what I'm looking for. We are assuming that email is going to
use the codec eventually so that it is not a bad thing to have charset
pre-populate the codec cache
R. David Murray added the comment:
The second line in that try: block should have been:
mime_name = ALIASES.get(python_name, python_name)
--
___
Python tracker
<http://bugs.python.org/issue8
R. David Murray added the comment:
REPL is the Python interactive prompt in this case (REPL is Read Eval Print
Loop). So Jesse is saying that using multiprocessing from the REPL (at least
on Windows) isn't supported. This is because on Windows multiprocessing needs
to re-import the
R. David Murray added the comment:
Not in email5. The RFC says that if the charset parameter isn't known you just
pass it through. In email6 we will be making a more careful distinction
between errors that should be passed silently per the RFC, and ones that should
be noisy because th
R. David Murray added the comment:
What I had in mind for the second test was something that did this (which I
think is legal from reading the docs):
parser.add_argument('foo')
parser.add_argument('bar', nargs='?', default='eggs')
with ass
R. David Murray added the comment:
For the record (for people reading this ticket later), the removal of the
python version of the unix subprocess code was discussed on IRC, and it was
clarified there that the reason for removing it is not that it duplicates the C
code. We like having
R. David Murray added the comment:
Why it works is due to a quirk in the handling of python strings: if an
apparent escape sequence doesn't "mean anything", it is retained verbatim,
including the '\' character. This is documented in
http://docs.python.org/refere
R. David Murray added the comment:
The fact that you have carefully think about which are escapes and which aren't
tells you that you should not be depending on the non-escapes not being
escapes. What if we added one? The doc says preserving the \s is a debugging
aid, and that is a
Changes by R. David Murray :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue12206>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
I like bitwise-or better than bitwise OR because 'bitwise-or' is a distinct
operation from 'or', and making it hyphenated emphasizes that.
--
___
Python tracker
<http://bug
Changes by R. David Murray :
--
nosy: +mark.dickinson
___
Python tracker
<http://bugs.python.org/issue12211>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
"Except when explicitly noted otherwise, all return values are floats."
On the other hand, copysign says "return x with the sign of y", which certainly
sounds like it is preserving x, not creating a new float. So at the least
there is
R. David Murray added the comment:
Everything in python is an instance of something. Objects all the way down...
>>> isinstance(object, object)
True
So, there is no function you are overlooking because there is nothing that is
not an instance.
--
nosy: +r.dav
R. David Murray added the comment:
You are correct, B is not an instance of A. But both B and A are instances of
'type':
>>> class A:
... pass
...
>>> class B(A):
...pass
...
>>> isinstance(A, type)
True
>>> isinstance(B, type)
True
>&
R. David Murray added the comment:
FYI that buildbot is likely to get a kernel upgrade in the not too distant
future.
--
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
You are confusing directives and roles. As was already pointed out, there is
currently no target for list.append to point to. That's what needs to be added.
--
nosy: +r.david.murray
___
Python tracker
R. David Murray added the comment:
The test_commands fix will be in 2.7.2. 2.7.1 was released well before the fix
was made.
--
___
Python tracker
<http://bugs.python.org/issue11
R. David Murray added the comment:
It should certainly be reported to the sphinx tracker where the right people to
make the decision for sphinx itself will see it. Then if the decision is that
type matters, python can decide how we want to handle that fact. Since the
core of sphinx does
R. David Murray added the comment:
> The deprecations for os.popenN() are still fine, since those
> APIs are not used all that much, and I'm sure that no one can
> really remember what all the different versions do anyway :-)
That's good, because those functions are alre
R. David Murray added the comment:
There were an awfully large number of pages of code for a thin wrapper.
Granted, half of that was probably os/2 support...
--
___
Python tracker
<http://bugs.python.org/issue6
R. David Murray added the comment:
I'm closing this as invalid/duplicate, but I'm sure this isn't the last time
we'll get this report. It would be nice if we could think of a way to improve
the situation.
--
nosy: +benjamin.peterson, r.david.murray
resolution:
R. David Murray added the comment:
I should have mentioned the bug number in the body, thanks for adding that.
FYI, the bug number also appears in the 'superseder' field, and (more
interesting to you in this context) if you just say, for example,
issue 12152 or #12152 ro
R. David Murray added the comment:
+1 to what Ezio said, though I'd rather have this than not have the
functionality at all :)
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Subprocess is throwing the correct exception, what it isn't doing is preserving
stderr. The stderr output in question is not coming from the *subprocess* (the
process hasn't been created yet). It would be nice if that stderr output could
be ad
R. David Murray added the comment:
Ah, I see. Agreed with the closing, then.
Cal: one way to debug this kind of thing is to try the same command with
shell=True. Then the shell will generate its special error message.
Changing the title back to something that might be recognizable to
R. David Murray added the comment:
Well, IIUC the Setup lines indicate where to find the system version of the
libraries (otherwise the included zlib is used). So I'm not at all sure that
there is a bug here. If you change Setup, you need to change it correctly for
your int
R. David Murray added the comment:
This is a general principle of how Python runs in interactive mode and is not
confined to loading readline. The same would be true for any module loaded
during startup, and there are quite a few that are so loaded. Since loading
modules from the current
R. David Murray added the comment:
I can't reproduce this. What exact version of Python are you using?
--
assignee: -> r.david.murray
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org
R. David Murray added the comment:
I think you are correct that the Availability can be removed, since the actual
limits of the support are exactly as complicated as the code that supports
them, and should give *some* result on most (all?) platforms. However, OS/X is
certainly covered by
R. David Murray added the comment:
No problem. It's too bad that regression slipped in to 3.2.0. I probably
fixed it by accident, since I rewrote a bunch of that code in 3.2.1 while
fixing a different bug.
--
resolution: -> out of date
stage: -> committed/rejected
s
R. David Murray added the comment:
As I recall the issue that triggered the change was reported by Michael Foord,
so I'm adding him as nosy too.
--
nosy: +michael.foord, r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Because 2.6 is in security-fix-only mode.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
The documentation is, in principle, wrong. The actual authority for the
"correct" implementation is PEP3101, which says the following:
The str.format() function will have
a minimalist parser which only attempts to figure out when it is
R. David Murray added the comment:
Note that the PEP also explicitly addresses your concern about getattr, as well
(validation of the name is delegated to the object's __getattr__).
--
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
Only because we had Macintosh in there. We don't mention OS/X explicitly
anywhere else in the docs that I could find (except one prose mention in the
logging docs).
--
___
Python tracker
<http://bugs.py
R. David Murray added the comment:
Georg: our post seem to have crossed despite Roundup's attempts at locking. +1
to your idea about the directive.
--
___
Python tracker
<http://bugs.python.org/is
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue11941>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
The mailbox module would benefit from having this precision available.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue11
R. David Murray added the comment:
I agree that the current situation is a bit murky and ought to be clarified,
but I'm going to leave it to Eric to point they way forward, as he is far more
knowledgeable about this area than I.
--
___
P
R. David Murray added the comment:
I would guess that if you instead skipped __dir__ completely for old style
classes it would expose a different bug in this or some other package.
--
___
Python tracker
<http://bugs.python.org/issue12
Changes by R. David Murray :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12263>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
This looks like a duplicate of #12204.
--
nosy: +r.david.murray
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> str.upper converts to title
___
Python tr
R. David Murray added the comment:
We don't currently support any flavor of VS2010. Since 2.7 is in bug fix mode
only, it is not clear that we will add such support. But since it is a long
term maintenance release the rules may be different.
--
nosy: +brian.curtin, l
R. David Murray added the comment:
I'm not sure I understand your confusion, but perhaps what you are missing is
that we don't support installing 3rd party packages inside a source tree, only
into an installed Python, and installing Python creates the site-packages
directory
R. David Murray added the comment:
Yes. If the directory gets created without Python being installed, then you
don't have a working python installation. Assuming we are talking about
site-packages. I have no idea what purelib is or anything about the packaging
inte
R. David Murray added the comment:
Your parenthetical reads sensibly to me, I can't think of a clearer alternative.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
-1 on adding the prototype (especially since I think it isn't always possible
to do so). In many cases it would make the message overlong, and the user can
look up the prototype by looking at their source code or using pydoc or their
IDE. The
R. David Murray added the comment:
That's why I said "their own source or pydoc...".
The language of the error message is trying to describe the error as the
interpreter knows about it at the time the error is generated. That has a
strong relationship to the prototype, but
R. David Murray added the comment:
I'm closing this as invalid. If someone wants to work on this feature, they'll
first have to add debugging to re
--
nosy: +r.david.murray
resolution: -> invalid
stage: -> committed/rejected
status
R. David Murray added the comment:
I've done a little poking around, and it looks like you are correct and I'm
wrong. It appears that readline.so is or should be a special case. I've added
some people to nosy to see what they think.
Specifically, it appears that if I put a f
R. David Murray added the comment:
Why was this issue set to pending? No motivating comment was added.
--
nosy: +r.david.murray
status: pending -> open
___
Python tracker
<http://bugs.python.org/iss
Changes by R. David Murray :
--
nosy: +lukasz.langa
___
Python tracker
<http://bugs.python.org/issue12274>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
Python 3.3a0 (default:7323a865457a+, Jun 5 2011, 19:22:38)
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.modules['log
R. David Murray added the comment:
Yeah, that would be my guess. And readline.so is imported in main at a point
where it has decided we are going into interactive mode, which is presumably
after all other initialization has taken place, including the path munging.
Thus my suggestion that
R. David Murray added the comment:
Um, no.
'pending' is 'pending close', specifically meaning, 'this issue is going to be
closed (with a rejected status of some sort) unless someone objects or provides
more information.'
Someday, pending issues will be a
R. David Murray added the comment:
I think you should just kill ast.__version__ in that case. There was a
discussion on python-dev and packaging about __version__ and PEP 396 was the
result. If you want the VCS info put it somewhere else (like __vcs_version__?).
--
nosy
Changes by R. David Murray :
--
nosy: -r.david.murray
___
Python tracker
<http://bugs.python.org/issue7511>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from R. David Murray :
After a make distclean I'm seeing the following output during a build of
default. It is possible my 2.7 install is borked, but I don't understand why
python is apparently being called during a gcc step. The build seems to
succeed.
gcc -pthr
Changes by R. David Murray :
--
nosy: +bethard
___
Python tracker
<http://bugs.python.org/issue12284>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
As far as I can tell my python2.7 installation is fine and bug free. hg is
working fine when called from the command line.
--
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
It turns out that I had a stray abc.py file in my current working directory as
the result of some previous tests of module-load-order rules. That by itself
wouldn't have triggered the problem, but in addition, I have PYTHONPATH set in
my enviro
R. David Murray added the comment:
See also #6827, just for some background on the current docs.
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue12
R. David Murray added the comment:
It requires adding code to support a new Sphinx directive. I'm not sure if it
should be a generic Sphinx directive (in which case we should open an issue on
the Sphinx bug tracker) or Python specific. If the latter, I can't at the
moment tell
R. David Murray added the comment:
"The required arguments are an RFC 822 from-address string, a list of RFC 822
to-address strings (a bare string will be treated as a list with 1 address)..."
--
resolution: -> invalid
stage: -> committed/rejected
status
R. David Murray added the comment:
With input from Michele on IRC I updated the tests to be more generic (not
depend on the order of the reported argument names) and moved the test I talked
about in my last message into a third unit test.
--
resolution: -> accepted
stage: ne
R. David Murray added the comment:
Thanks for the report. I broke that when I refactored the code, and
unfortunately there was no existing test that tested dot quoting. There is now.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -&g
R. David Murray added the comment:
While I don't understand the zip file structure enough to do a definitive
review of the patch, I'm willing to take processing 50K zip files successfully
as a definitive test :)
--
resolution: -> fixed
stage: patch review -> co
R. David Murray added the comment:
Note that based on the fact that most zipfile tools handle garbage after the
indicated end of the comment by ignoring it, #10694 fixed zipfile to also
ignore such trailing data.
It sounds like there may be more out-of-spec errors that could be ignored
R. David Murray added the comment:
Here is an updated patch with the tests refactored even further. The patch
seems correct to me, and almost all the comment tests fail before the patch and
pass after.
Benjamin, this patch fixes a regression relative to 2.7.1 and 3.1.3, so I'm
setti
R. David Murray added the comment:
lexer.instream.readline(): no, we can't just call that without the seek,
because reading the token that started with # may have caused the line to be
consumed already. I've expanded the comment to explain this.
cygwin: I'd add a comment if I
R. David Murray added the comment:
This should not be applied until after the patch for #12009 is applied, at
which point the test will need to be adjusted. #12009 completely refactors the
netrc test suite.
I wonder if the 'hosts' attribute should be deprecated, but let&#x
R. David Murray added the comment:
Improvements are welcome, the whole thing was a QnD hack that has been evolving
over time...maybe there's some way to reuse unittest's assertEqual machinery?
I also wonder if the whole environment-changed thing should be moved into
unittest so it
Changes by R. David Murray :
--
stage: -> needs patch
type: -> feature request
___
Python tracker
<http://bugs.python.org/issue12314>
___
___
Python-bugs-
Changes by R. David Murray :
--
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
R. David Murray added the comment:
I agree with Petri, so I'm setting this to a doc issue.
--
assignee: -> docs@python
components: +Documentation
nosy: +docs@python, r.david.murray
stage: -> needs patch
type: -> behavior
___
Python
R. David Murray added the comment:
I think it would be good to mention the numeric levels in the text as well (in
parenthesis, perhaps), unless the rest of the logging docs no longer refer to
the numeric levels.
--
nosy: +r.david.murray
___
Python
R. David Murray added the comment:
Sometimes we use the patch keyword for doc issues where someone has suggested a
specific new wording but not generated an actual patch. That seems to be the
case here.
--
nosy: +r.david.murray
___
Python tracker
Changes by R. David Murray :
--
versions: -Python 3.1
___
Python tracker
<http://bugs.python.org/issue11669>
___
___
Python-bugs-list mailing list
Unsubscribe:
R. David Murray added the comment:
fileno and stat won't work on a StringIO object. So StringIO would need to be
special cased to call getvalue.
--
nosy: +orsenthil, r.david.murray
___
Python tracker
<http://bugs.python.org/is
R. David Murray added the comment:
According to this ticket it hasn't been applied anywhere yet (a message will be
posted here when it is).
--
nosy: +r.david.murray
versions: +Python 3.3 -Python 3.1
___
Python tracker
<http://bugs.py
R. David Murray added the comment:
But if the len information is available, why not return it?
--
___
Python tracker
<http://bugs.python.org/issue12327>
___
___
Changes by R. David Murray :
--
versions: +Python 3.2 -Python 2.6
___
Python tracker
<http://bugs.python.org/issue12327>
___
___
Python-bugs-list mailin
R. David Murray added the comment:
Is it really necessary to copy this file? I haven't looked at the tests, but
I'm wondering if they are using xxmodule.c only because it already existed.
Could the test instead use a much simpler .c file that it creates on the fly?
-
R. David Murray added the comment:
IIUC, collections.Set is, by definition, the full 'set' API. The fact that the
set builtin implements some additional methods is a convenience.
--
nosy: +r.david.murray, rhettinger
___
Python trac
R. David Murray added the comment:
collections.Set (in python 3.3, collections.abc.Set) is the *definition* of the
minimal API. To construct a class that conforms to the minimal definition is
certainly easier than constructing one that supports all of the methods that
the set builtin does
R. David Murray added the comment:
The code you are suggesting patching is trying its best to return a length. If
that code needs to be fixed to not throw an error when confronted with a
StringIO, then it should do its best to return a length. Your original message
on the ticket did not
R. David Murray added the comment:
I normally build using --prefix, often with --prefix=/dev/null, and I can't
recall any version not building zlib. Of course, I don't uncomment the zlib
entry in Modules/Setup.
As far as I can see the zlib entry is unique in Setup in using pre
101 - 200 of 10554 matches
Mail list logo
