Eric Smith added the comment:
I think I'd just delete both instances of "now". And now that I read it more
critically, "position" should be "positional". How's this rewording:
.. versionchanged:: 2.7
The positional argument specifiers can be omi
Eric Smith added the comment:
Looks good.
--
___
Python tracker
<http://bugs.python.org/issue9139>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eric Wald added the comment:
Reproduced again in version 2.7rc2; I had thought that it went away, but it
turns out that --with-pydebug hides the problem.
Compiling GDB now.
--
status: pending -> open
versions: +Python 2.7
___
Python tracker
&l
Eric Smith added the comment:
+1 from me, too.
You might want to reference this issue in the Misc/NEWS entry.
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue9
Eric Smith added the comment:
I get the same behavior in 2.7. Adding '--', I get:
>>> p.parse_args('-b 123 456 -- bla'.split())
Namespace(bar=[123, 456], foo='bla')
Which is what I expect.
Éric: From your comment, I'm not sure if you think it
Eric Smith added the comment:
Surely we don't want to find every place that uses structseq and fix them. This
will no doubt break user code as well.
I think we'll need to fix structseq to somehow have its old behavior.
--
nosy: +
Eric Smith added the comment:
The note about no quoting meta-chars is in the docstring for fnmatch.translate,
not the documentation. I still see it in 3.1. I have a to-do item to add this
to the actual documentation. I'll add an
Changes by Eric Smith :
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue9226>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eric Smith added the comment:
Excellent explanation. It's just a misunderstanding of how the language works,
so nothing to do here. Closing.
--
nosy: +eric.smith
resolution: -> invalid
status: pending -> closed
___
Python tra
New submission from Eric Talevich :
In xml.etree, ElementTree and cElementTree implement different interfaces for
the iterparse function/class.
In ElementTree, the argument "events" must be a tuple of strings:
from xml.etree import ElementTree as ET
for result in ET.iterparse(&#
Changes by Eric Smith :
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue9265>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eric Smith added the comment:
The change looks reasonable to me. It needs a test.
--
nosy: +eric.smith
stage: -> unit test needed
___
Python tracker
<http://bugs.python.org/iss
Eric Smith added the comment:
I believe it's true that Windows does not offer process replacement. I'm sure
you could perform some tricks by essentially writing your own loader, but the
practical answer is no. It might be worth looking into how cygwin implements
exec().
-
New submission from Eric Promislow :
Similar to bug http://bugs.python.org/issue5215 which found
a workaround in pdb. Here I want to use code.InteractiveInterpreter
to modify code interactively (see Komodo bug
http://bugs.activestate.com/show_bug.cgi?id=87405 )
I can do this at the top-level
Eric Promislow added the comment:
I've modified the bug status so anyone can read it. You
don't need an account to read ActiveState bugs, only to
add or comment on one.
Please note that I closed bug
http://bugs.activestate.com/show_bug.cgi?id=87405, as we're now w
Eric Promislow added the comment:
Thanks for the response.
Note that our use case *is* to implement Python-console
functionality, but sometimes we do this in the context
of a currently running Python program, inside a function.
That's why I wrote the repro that way.
Eric Promislow added the comment:
David, that won't work for a reason I'll get into in a bit.
I would drop the priority of this ... Komodo has a had a
Python debugger since late 2000, we only fixed updating
variables while debugging (using the variable viewer) yesterday,
and rece
Eric Smith added the comment:
Yes, the unicode patch looks okay to me.
--
___
Python tracker
<http://bugs.python.org/issue9036>
___
___
Python-bugs-list mailin
Eric Smith added the comment:
I'm not sure where you'd put this. The defining characteristic of threads is
that _all_ objects are shared among them.
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.
Eric Smith added the comment:
Yes, that is what it says; and yes, it should be "string". Although why all of
the methods say "string" and not "str" isn't clear to me. Probably historical.
The doc string for str.__format__ contains the same e
Eric Smith added the comment:
And now that I look at it, the subject contains "__format__" but the original
message says "format". Both cases are already covered!
--
___
Python tracker
<http://bu
Changes by Eric Smith :
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue9332>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Eric Smith :
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue9334>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eric Smith added the comment:
Wouldn't you have to set this, then restore it? This would then open a non
thread-safe race condition, assuming this is a per-process setting, not a
thread-local setting.
Not that I'm necessarily opposed, but it&
Eric Talevich added the comment:
This issue still occurs when the name "long" is a function argument:
def double(long):
return long * 2
2to3 converts it to:
def double(long):
return int * 2
Should I file a new bug, or can someone reopen this?
--
nosy: +eri
Eric Smith added the comment:
I think this is a good idea. To test how much impact it would have, I changed
float's str to return the same value as repr. regrtest broke only 3 tests:
test_float test_tokenize test_unicodedata. It's not clear to me why unicodedata
failed.
With s
Eric Smith added the comment:
I think under the "we're all consenting adults" doctrine that it should be
allowed. If you really want that behavior, why force the char*/%s dance at each
call site when it's easy enough to do it in one place? I don't think anyone
suppl
Eric Smith added the comment:
The feature request seems reasonable to me, too.
I don't recall if sys.getdefaultencoding() can change while a program is
running. If so, you might want to change:
def read(self, filenames, encoding=sys.getdefaultencoding()):
to:
def read(self, file
Eric Smith added the comment:
I agree this should be closed and moved to #8350.
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue9
Changes by Eric Smith :
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue8350>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eric Smith added the comment:
I think it would be clearer if the footnote said something like "Negative 1 day
plus 19 hours is equivalent to the timedelta argument of -5 hours)". If I
hadn't been following the discussion on #python-dev the point of this doc
change would have
Changes by Eric Smith :
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue9503>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Eric Smith :
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue9530>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Eric Smith :
--
nosy: +eric.smith
___
Python tracker
<http://bugs.python.org/issue9537>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eric Smith added the comment:
I don't think it would be covered by the moratorium, since it's not a language
change. The change to make structseq derive from tuple was not subject to the
moratorium, for example.
--
___
Python trac
Eric Smith added the comment:
I agree with Steven: for the current tests we should specify (and restore) 80
columns. We might want to add additional tests at different column widths.
--
___
Python tracker
<http://bugs.python.org/issue9
Eric Appelt added the comment:
Hi, I'm a new contributor trying to get started with documentation and testing.
I have been following and testing PEP525 and PEP530 and feel familiar enough to
try to work on adding this to the Python Language Reference if it would not be
redundant with
Eric Lafontaine added the comment:
Hi, Not sure this is where the comment goes...
I work with the smtplib and email libraries. I understand Henning von Bargen
when he say that we should have a way to support RFC 5322 without asking the
user to understand how to support it. The issue is
Eric Appelt added the comment:
Hi Yury - Yes, I am excited about doing this and getting to work on it. Today
was pretty busy but I have some time blocked out tomorrow to really dig in. I
was planning to give myself a deadline of Friday afternoon if that works for
the review/release schedule
New submission from Eric Appelt:
While testing my understanding in order to document PEP525 asynchronous
generators in the Language Reference (issue 28091) I noticed that the
implemented behavior deviates from PEP525, specifically the PEP states that:
"When an asynchronous generat
Eric Appelt added the comment:
I think this needs considerable checking and polishing, but I am submitting
this "Work In Progress" patch for the PEP525 and PEP530 documentation so that I
can get some general feedback since I am new to this, and to ensure that if
this is not generall
Eric Appelt added the comment:
Yes - I'll work on the patch tonight.
--
___
Python tracker
<http://bugs.python.org/issue28091>
___
___
Python-bugs-list m
Eric Appelt added the comment:
I believe that I addressed all the comments in the previous review (although
its always possible I missed something), and have a new patch with the
improvements and fixes.
I also noticed that in asyncio, loop.shutdown_asyncgens() is a coroutinemethod
and fixed
Eric Appelt added the comment:
Thanks for the explanations and example code in the review! Working on this
issue is really helping to improve my understanding of a number of tricky
things like finalization.
I *think* that I have all the comments implemented in the attached patch.
I also
Eric Lafontaine added the comment:
Hi,
I believe it's already done. The only thing that people tends to forget is
that doing python -m "module.script(.py)" is only doing the equivalent of
"python module/script.py".
I believe it's clear though ;
https://docs.p
Eric Lafontaine added the comment:
Hi all,
Thanks for the enlightment. I never figured that there was a send_message
function XD. Never needed it and it's true that the example in the email
library use sendmail and not send_message.
https://docs.python.org/2/library/smtplib
Eric Lafontaine added the comment:
Hi all, I was looking at the code of the function and also noticed multiple
"itching".
1- Why raise an error when 2 resent-date exist? it may exist and completely
legitimate as per RFC5322. The code should always take the first one it sees
as p
Eric Lafontaine added the comment:
Hi all,
this is not a short answer, like I hoped it would be ;). But skip to the last
section if you don't want to read it all.
the heuristic problem :
For the heuristic of the resent headers, it's clearly say in t
Eric Lafontaine added the comment:
forgot to re-post the to-do, and to correct the documentation :
List of things to do :
- Implement a patch for the code to add a missing "Date" field if it doesn't
exist . (in review)
- Modify the documentation at the SMTPLib for the send_mes
Eric Lafontaine added the comment:
Hi all,
@David, the "Resent-" block should be added by the user and he needs to know
what he's doing. Hell, I work with emails all the time and never knew about
this. The Worse part of it is that I have to communicate with the IETF just to
Eric Lafontaine added the comment:
Hi all,
I believe this is the right behavior and what ever generated the boundary
"<<>>" is the problem ;
RFC 2046 page 22:
_
The only mandatory global parameter for the "multipart" media type is the
bo
Eric Lafontaine added the comment:
Hi all,
I hate this proposition. I feel it's a "victory" for the people who don't want
to follow RFC standard and allow "triple"-quoting on things that aren't
supposed to...
Now that my opinion is said, I made 2 te
Eric Lafontaine added the comment:
N.B., I've tried to do the keyword parameter on the get_param inside the
get_boundary as well as I though it was a good Idea as well, but it was
breaking some test cases (multiple ones). So I didn't pursue.
N.B. I'm guessing (guessing) unquo
Eric Appelt added the comment:
I would be happy to work on a documentation patch for this - I'll try to have
something up by tomorrow evening if no one beats me to it.
--
nosy: +Eric Appelt
___
Python tracker
<http://bugs.python.org/is
Eric Lafontaine added the comment:
overkill file
--
Added file: http://bugs.python.org/file46002/issue_28879_python2_overkill.patch
___
Python tracker
<http://bugs.python.org/issue28
Eric Lafontaine added the comment:
Hi David, Henning,
Sorry for the delay. Here is the patch for python 2... but I find that adding
an "example" just for RFC 5322 is kind of over-kill...
So I've made both :) please choose which one you prefer and let me know. I
personnall
Eric Lafontaine added the comment:
Hi,
I would like to have a bigger set of user testing this patch before it gets
approve... I really don't know all the extent to which it's a good/bad idea.
The proposition was to not do the unquote in the rfc2231 collapse method. It
doe
Eric Lafontaine added the comment:
Hi,
I would like to thank you for keeping up with me. I may not be easy at times,
but please make me understand if it doesn't make sense :).
Thanks bpoaugust and David,
Eric Lafontaine
--
___
Python tr
Eric Appelt added the comment:
I looked at the documentation and implementation and made a patch to hopefully
clarify the issue. I also have some comments:
- The term "epoch" is actually defined at the top of the page with instructions
for how to determine it, i.e. run "gmtime(
Eric Appelt added the comment:
I had some checks performed on a Windows platform using the following snippet:
# valid for 2016
import time
def check():
t = time.gmtime()
print(46*86400*365 + 11*86400 + (t.tm_yday-1)*86400 + t.tm_hour*3600 +
t.tm_min*60 + t.tm_sec)
print(time.time
New submission from Eric Snow:
Currently there isn't any way to uniquely identify an interpreter. This patch
adds a new "id" field to the PyInterpreterState struct. The ID for every new
interpreter is set to the value of an increasing global counter. That means
that the ID i
Eric Snow added the comment:
Pointers can get re-used, so they aren't temporally unique.
--
___
Python tracker
<http://bugs.python.org/issue29102>
___
___
Eric Snow added the comment:
Three reasons come to mind:
1. threads are identified by small integers
2. long, random-looking IDs are not human-friendly, and subinterpreter IDs will
be used like thread IDs are
3. related to what Steve said, temporally unique IDs allow us to be confident
about
Eric Snow added the comment:
Interpreter states are in a linked list, so you
can traverse the list to find one by ID.
Exactly. At first I had added a PyInterpreterState_FindByID() or something
like that. However, as you noted, I realized it wasn't necessary. :)
WRT weakrefs, we can&
Changes by Eric Lafontaine :
--
nosy: +Eric Lafontaine
___
Python tracker
<http://bugs.python.org/issue29020>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eric Lafontaine added the comment:
Hi all,
The fix is already provided in issue28945 . Please review it and I would like
to flag it as needing more test on more version of python...
The patch would just require more Test Case that would check for the
filename for preventing re-occurence in
Eric Snow added the comment:
> What do you think about resetting the counter back to 1 in Py_Initialize?
Sounds good to me. When I was working on the patch I had the idea in the back
of my mind that not resetting the counter would better support interpreter
separation efforts in the fut
Eric Snow added the comment:
Here's the updated patch.
--
Added file: http://bugs.python.org/file46094/interpreter-id-2.diff
___
Python tracker
<http://bugs.python.org/is
Eric Snow added the comment:
int_fast64_t it is then. :) I vacillated between the options and went with the
bigger space. However, you're right that following convention is worth it.
--
___
Python tracker
<http://bugs.python.org/is
Eric Snow added the comment:
I've updated the patch to address Nick's review. Thanks!
--
Added file: http://bugs.python.org/file46100/interpreter-id-3.diff
___
Python tracker
<http://bugs.python.o
Eric Snow added the comment:
Thanks for pointing that out, Victor. Given the precedent I switched to using
int64_t. The patch actually uses PY_INT64_T, but I didn't see a reason to use
int64_t directly. FWIW, there *are* a few places that use int_fast64_t, but
they are rather specia
New submission from Eric Ahn:
On this page of the documentation
https://docs.python.org/3/library/asyncio-subprocess.html it seems that some of
the reference names are incorrect.
Namely, asyncio.subprocess.PIPE is referred to as
asyncio.asyncio.subprocess.PIPE (along with STDOUT and DEVNULL
Eric Snow added the comment:
There shouldn't be anything in CPython that depends on IPython. I'd recommend
checking for $PYTHONSTARTUP, in site.py, and for .pth files in directories on
sys.path. Also look for .py files in the current directory that are shadowing
stdlib module
Eric Fahlgren added the comment:
> # Junctions are not recognized as links.
> self.assertFalse(os.path.islink(self.junction))
If the above comment is intended as a statement of fact, then it's inconsistent
with the implementation of Py_DeleteFileW (
https://hg.python.org/c
Eric Lafontaine added the comment:
Hi all,
The IETF didn't answer yet :(.
I'll await your news regarding this patch ("issue_28879_V4.patch").
I would like to have feedback if I need to change something.
Thanks a lot in adva
Eric Lafontaine added the comment:
Hi all,
I've received an answer from the IETF Pete Resnick. The answer does say
however that there is no guaranteed way of getting the right headers if the
message doesn't respect the standard;
"[...]
In this case, if the trace fields w
Eric Lafontaine added the comment:
Hi,
I've implemented the heuristic, but it's messy with the issue of this ticket.
I'm going to do some clean-up and separate the issue from the heuristic and
post them separated.
Date issue ;
Test Case
Documentation
Implementation
Heur
Changes by Eric Fahlgren :
--
nosy: +eric.fahlgren
___
Python tracker
<http://bugs.python.org/issue29282>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eric Lafontaine added the comment:
Resent-heuristic
--
Added file: http://bugs.python.org/file46460/Resent_heuristic.patch
___
Python tracker
<http://bugs.python.org/issue28
Eric Lafontaine added the comment:
Hi all,
Here you go :).
Regards,
Eric Lafontaine
--
Added file: http://bugs.python.org/file46459/issue28879_v5.patch
___
Python tracker
<http://bugs.python.org/issue28
Eric Lafontaine added the comment:
Hi,
I've just watched the old David Beazley video about the packaging system in
python and got me thinking about this issue.
I'm throwing the idea, please critize it!
If we were to make a "hook" for the .rst files of the modules to go an
Eric Lafontaine added the comment:
Hi all,
What do we do with this ticket?
Patch were provided, People have agreed (I think). So what's missing to close
it (or pass to the next step)? It's going to be a year that a high priority
ticket has no update and I would like to accelera
Eric Lafontaine added the comment:
Hi,
For user-defined class, it's up to the class to do the right implementation in
my opinion. It's true the description is wrong though.
x in y means that x exist inside of y (so that the execution of
y.__contain__(x) is executed successfully an
Eric Lafontaine added the comment:
Hi all,
Here are the test I've made to understand the behavior :
class Foo_42(object):
def __contains__(self,item): return 42
class Foo_neg(object):
def __contains__(self,item): return -42
class Foo_None(object):
def __contains__
Eric Lafontaine added the comment:
Hi David, sorry for the delay on my part for providing how I was getting to
that conclusion. I've also resurrected an old post as I want to start
contributing more seriously :).
As this is documentation only (not changing the code behavior), I didn
Eric Lafontaine added the comment:
oh, I've got what you meant!
Proposed change :
For user-defined classes which define the __contains__() method, the in
operator will convert to False "x in y" if y.__contains__(x) return False, 0 or
None. Otherwise, the in operator will retu
Eric Lafontaine added the comment:
(first time trying to reply through email)
thanks for the example and you are right :
class Foo_emptylist(object):
def __contains__(self,item): return []
class Foo_emptydict(object):
def __contains__(self,item): return {}
class Foo_emptystring(object
Eric Snow added the comment:
This is strictly a problem for the system Python, right? In that case, can't
the dist package clear __pycache__ under the system site-packages directory
(and any other user-read-only dirs) during install of the updated Python?
Is the concern that upgrading P
Eric Appelt added the comment:
As we have moved to GitHub and mandatory reviews with Pull Requests, I have
created a new patch in PR#34 which incorporates Victor's suggestions.
--
___
Python tracker
<http://bugs.python.org/is
Eric Appelt added the comment:
I added PR #54 with a test as Nick describes for checking magic number changes
and explaining to the developer the procedure to follow if this is required in
a maintenance release.
--
nosy: +Eric Appelt
pull_requests: +49
Eric Snow added the comment:
> These files *do not* belong to the CPython package, they belong to the
> individual Python modules that depend on CPython, so messing with them
> when installing a new version of CPython would be a significant breach
> of distro policies.
Thanks fo
Changes by Eric Appelt :
--
pull_requests: +91
___
Python tracker
<http://bugs.python.org/issue29026>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eric Lafontaine added the comment:
Hi,
Could someone put this ticket on "waiting for review"?
Regards,
Eric Lafontaine
--
___
Python tracker
<http://bugs.python.o
New submission from Eric Snow:
Looks like we weren't careful when we added find_spec(). :) This issue is just
to track the change. I'll push the fix shortly.
--
assignee: eric.snow
messages: 266506
nosy: brett.cannon, eric.snow
priority: normal
severity: normal
stage: n
Changes by Eric Snow :
--
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
New submission from Eric Snow:
PEP 420 should be mentioned in the introduction section of the importlib docs.
I'll push a change to fix this in a minute.
--
assignee: eric.snow
components: Documentation
messages: 266565
nosy: brett.cannon, eric.snow
priority: normal
severity: n
Changes by Eric Snow :
--
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Eric Snow added the comment:
Thanks. Yeah, I wanted to keep the patches separate for the sake of code
review. I'll fold the changes into a single commit once everything's ready.
--
___
Python tracker
<http://bugs.python.o
Eric Snow added the comment:
Here's the full patch, including the addition of __definition_order__, tests,
and docs.
--
Added file: http://bugs.python.org/file43168/deforder.diff
___
Python tracker
<http://bugs.python.org/is
Changes by Eric Snow :
Removed file: http://bugs.python.org/file43168/deforder.diff
___
Python tracker
<http://bugs.python.org/issue24254>
___
___
Python-bugs-list mailin
3301 - 3400 of 6654 matches
Mail list logo
