[issue518985] Ellipsis semantics undefined

Change by admin : -- github: None -> 36117 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue476194] dir(Ellipsis)

Change by admin : -- github: None -> 35425 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Pablo Galindo Salgado added the comment: New changeset 3283bf4519139cf62ba04a76930f84ca1e7da910 by Pablo Galindo in branch '3.10': [3.10] bpo-44273: Improve syntax error message for assigning to "..." (GH-26477) (GH-26478)

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Change by Pablo Galindo Salgado : -- pull_requests: +25073 pull_request: https://github.com/python/cpython/pull/26478 ___ Python tracker ___

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Pablo Galindo Salgado added the comment: New changeset 39dd141a4ba68bbb38fd00a65cdcff711acdafb5 by Serhiy Storchaka in branch 'main': bpo-44273: Improve syntax error message for assigning to "..." (GH-26477) https://github.com/python/cpython/commit/39dd141a4ba68bbb38fd00a65cdcff711acdafb5

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Change by Serhiy Storchaka : -- keywords: +patch nosy: +serhiy.storchaka nosy_count: 2.0 -> 3.0 pull_requests: +25072 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26477 ___ Python tracker

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Andre Roberge added the comment: Up to your best judgment Pablo - and thanks for your ongoing work on improving error messages. -- ___ Python tracker ___

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Pablo Galindo Salgado added the comment: I suggest to just close it or otherwise changing the message to include "..." instead of "Ellipsis". Anything else is actually much more complex than it seems, unfortunately -- ___ Py

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Andre Roberge added the comment: > > I think that the suggestion to explicitly refer to '...' instead of the name Ellipsis would be preferable. Aside: I had not realized that this was done at a different stage for __debug__ and Ellipsis ("Ignorance is bliss"...

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Pablo Galindo Salgado added the comment: What we can do is to replace: SyntaxError: cannot assign to Ellipsis here. Maybe you meant '==' instead of '='? for SyntaxError: cannot assign to '...' here. Maybe you meant '==' instead

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Pablo Galindo Salgado added the comment: Also, another problem is that "cannot assign to __debug__" is actually a compiler error, while "cannot assign to Ellipsis here. Maybe you meant '==' instead of '='?" is a parser error. This is because "__debug__&quo

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Pablo Galindo Salgado added the comment: Hu, I sort of agree, but I need to weigh how complex is going to be to special-case. I really don't want to start adding many different paths for the different built-ins in different situations. -- ___

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

Change by Batuhan Taskaya : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44273] Assigning to Ellipsis should be the same as assigning to __debug__

New submission from Andre Roberge : Consider the following in Python 3.10 >>> ... = 1 File "", line 1 ... = 1 ^^^ SyntaxError: cannot assign to Ellipsis here. Maybe you meant '==' instead of '='? >>> __debug__ = 1 File "", line 1 SyntaxError

[issue12056] "…" (HORIZONTAL ELLIPSIS) should be an alternative syntax for "..." (FULL STOP FULL STOP FULL STOP)

Xavier Morel added the comment: > But if we allow for ellipsis, then would we not also have to start allowing > characters like ≥ and ≤ in Python? No, they're not defined as canonically equivalent to >= and <= by the Unicode specification: >>> unicod

[issue43676] Doctest ELLIPSIS explanation hard to follow when they're missing

New submission from Tim Hatch : The doctest docs try to explain directives like ELLIPSIS but those directives are absent from the rendered html. Where? Most of the code blocks in the Directives section, and https://docs.python.org/3/library/doctest.html#directives and the one introduced

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

Jason R. Coombs added the comment: Today I encountered another situation where it would be convenient to allow an ellipsis at the beginning of the syntax: >>> pathlib.Path('abc') ...Path('abc') Because pathlib.Path resolves to `PosixPath` and `WindowsPath` depending on the

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

Jason R. Coombs added the comment: I've encountered this issue again with a different use-case. I'm attempting to add a doctest to a routine that emits the paths of the files it processes. I want to use ellipses to ignore the prefixes of the output because they're not pertinent to the test.

[issue9640] Improved doctest REPORT_*DIFFs with ELLIPSIS and/or NORMALIZE_WHITESPACE

Change by Raymond Hettinger : -- nosy: +tim.peters ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9640] Improved doctest REPORT_*DIFFs with ELLIPSIS and/or NORMALIZE_WHITESPACE

Irit Katriel added the comment: The patch needs to be converted into a github PR. Trevor, are you interested in doing that? -- nosy: +iritkatriel ___ Python tracker ___

[issue41652] An Advice on Turning Ellipsis into Keyword

Josh Rosenberg added the comment: I'm closing this as not being worth the costs of adding new keywords. You're welcome to propose it on the python-ideas list (a more appropriate place to propose and suss out the details of significant language changes), but you'll need to formulate a much

[issue41652] An Advice on Turning Ellipsis into Keyword

Serhiy Storchaka added the comment: There is Ellipsis class in the ast module. Although it is deprecated now. But I there may be Ellipsis names also in third-party libraries. Making Ellipsis a keyword would break them. -- nosy: +serhiy.storchaka

[issue41652] An Advice on Turning Ellipsis into Keyword

Josh Rosenberg added the comment: You can do the same thing to replace int, float, dict, len, and all the other built-in classes and functions. Why is Ellipsis so special that it needs protection, especially when, as you note, ... is an available unoverrideable way to refer to it? Making

[issue41652] An Advice on Turning Ellipsis into Keyword

New submission from Alex <2423067...@qq.com>: In early versions of python, programmers can simply swap True and False by >>> True, False = False, True Then True and False and None become keywords so programmers can't change their value. ... is also a keyword, but Ellipsis is n

Re:syntax for ellipsis like as "net.blobs['data'].data[...] = transformed_image"

Thanks too, I have find the answer from "https://stackoverflow.com/questions/772124/what-does-the-python-ellipsis-object-do; This came up in another question recently. I'll elaborate on my answer from there: Ellipsis is an object that can appear in slice notation. For example: myLis

syntax for ellipsis like as "net.blobs['data'].data[...] = transformed_image"

0, 3, 227,227) net.blobs['data'].data[...] = transformed_image 1. For ellipsis, is there syntax in python like this " net.blobs['data'].data[...]"? I have checked it which the type is "" 2. Could you provide some samples in which need to use ellipsis.

[issue36714] Tweak doctest 'example' regex to allow a leading ellipsis in 'want' line

Brian Skinn added the comment: On reflection, it would probably be better to limit the ELLIPSIS to 3 or 4 periods ('[.]{3,4}'); otherwise, it would be impossible to express an ellipsis followed by a period in a 'want'. -- ___ Python tracker

[issue36714] Tweak doctest 'example' regex to allow a leading ellipsis in 'want' line

Brian Skinn added the comment: I suppose one alternative solution might be to tweak the ELLIPSIS feature of doctest, such that it would interpret a run of >=3 periods in a row (matching regex pattern of "[.]{3,}") as 'ellipsis'. The regex for PS2 could then have a negative lo

[issue36714] Tweak doctest 'example' regex to allow a leading ellipsis in 'want' line

uch a case, "..." could mark either (1) an ellipsis standing in for an entire line of 'want', or (2) a PS2, marking a blank line in 'source'. I don't really think aggressive lookahead would help much -- an arbitrary number of following lines could contain exactly "...", and the int

[issue36714] Tweak doctest 'example' regex to allow a leading ellipsis in 'want' line

Paul Moore added the comment: It shouldn't be hard to update the regex to accept either "... " followed by other text or "..." on a line on its own, surely? -- nosy: +paul.moore ___ Python tracker

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

Michael Blahay added the comment: At the end of msg309603 it was stated that this issue is being changed to an enhancement. Later on, Tim Peters changed it Type back to behavior, but didn't provide any detail about why. Should this issue still be considered an enhancement? -- nosy:

[issue36714] Tweak doctest 'example' regex to allow a leading ellipsis in 'want' line

bar 7] baz If line 3 contains exactly "..." instead of starting with "... ", it will not be recognized as a PS2 line and the example will be parsed as: 'source' >>> def foo(): ...print("bar") 'want' ... ...print("baz") IMO this isn't a *ter

[issue36714] Tweak doctest 'example' regex to allow a leading ellipsis in 'want' line

behavior is consistent across 3.4.10, 3.5.7, 3.6.8, 3.7.3, and 3.8.0a3. **However**, in this `ell_print.py` above, that "PS2" line isn't actually meant to be a continuation of the 'source' portion of the example; it's meant to be the *output* (the 'want') of the example, with a leadi

[issue34817] Ellipsis docs has extra dot in the markdown that makes it look like .... (four dots)

Change by Karthikeyan Singaravelan : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue34817] Ellipsis docs has extra dot in the markdown that makes it look like .... (four dots)

Karthikeyan Singaravelan added the comment: Thanks Martin for the suggestion. I have created a PR with your suggestion and added a description in the PR that shows the visual distinction between the current doc and suggested change. -- ___ Python

[issue34817] Ellipsis docs has extra dot in the markdown that makes it look like .... (four dots)

Change by Karthikeyan Singaravelan : -- keywords: +patch pull_requests: +9140 stage: -> patch review ___ Python tracker ___ ___

[issue34817] Ellipsis docs has extra dot in the markdown that makes it look like .... (four dots)

Martin Panter added the comment: In these situations, I use quotes or brackets to mention a symbol without using it as punctuation. Using words might also help. What about: Ellipsis The same as the ellipsis literal “...”. Special value used [etc] -- nosy: +martin.panter

[issue34817] Ellipsis docs has extra dot in the markdown that makes it look like .... (four dots)

New submission from Karthikeyan Singaravelan : I looked up the Ellipsis documentation at https://docs.python.org/dev/library/constants.html#Ellipsis which has the below text : > The same as Special value used mostly in conjunction with extended > slicing syntax for user-d

[issue33739] pathlib: Allow ellipsis to appear after "/" to navigate to parent path

Yury Selivanov added the comment: Since nobody likes the idea I'm withdrawing the proposal. -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue33739] pathlib: Allow ellipsis to appear after "/" to navigate to parent path

Brett Cannon added the comment: I'm personally not loving the idea either by re-purposing Ellipsis for this since my brain keeps thinking you're trying to go two levels up instead of just one with that extra dot. It should also be mentioned that paths ending in an ellipsis has actual

[issue33739] pathlib: Allow ellipsis to appear after "/" to navigate to parent path

Timo Furrer added the comment: > I've just tried, "..." doesn't seem to mean anything on the Windows CLI. It's not only about Windows / Linux here - it's about the shell and command which is being used. If we talk about "cd" for example - it's a builtin in most common shells on Linux, which

[issue33739] pathlib: Allow ellipsis to appear after "/" to navigate to parent path

Antoine Pitrou added the comment: I've just tried, "..." doesn't seem to mean anything on the Windows CLI. But I agree with the reservation that having "..." mean something different than ".." is a recipe for confusion. -- nosy: +steve.dower ___

[issue33739] pathlib: Allow ellipsis to appear after "/" to navigate to parent path

Serhiy Storchaka added the comment: Note that 'a/b/c/..' is not the same as 'a/b' if 'c' is a link. And since "p / ..." looks very similar to "p / '..'", it will cause mistakes. "p.parent" is more explicit. AFAIK in cmd.exe on Windows 'a/b/c/...' means 'a/b/c/../..'. This is yet one source

[issue33739] pathlib: Allow ellipsis to appear after "/" to navigate to parent path

Change by Yury Selivanov : -- keywords: +patch pull_requests: +6958 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue33739] pathlib: Allow ellipsis to appear after "/" to navigate to parent path

/ 'temp' PosixPath('a/temp') The patch is trivial and I think that using "..." instead of ".parent" makes code clearer and cuter. -- components: Library (Lib) messages: 318468 nosy: brett.cannon, pitrou, yselivanov priority: normal severity: normal stag

Re: ... (ellipsis)

On Thu, May 31, 2018 at 11:00:13PM -0400, Terry Reedy wrote: > On 5/31/2018 10:26 PM, Mike McClain wrote: > > I'm having understanding the use if the ellipsis. > >I keep reading that it is used in slices > > By numpy for numpy multidimensional arrays, which have their own

Re: ... (ellipsis)

On 5/31/2018 10:26 PM, Mike McClain wrote: I'm having understanding the use if the ellipsis. I keep reading that it is used in slices By numpy for numpy multidimensional arrays, which have their own __getitem__, which recognizes and gives meaning to ... -- Terry Jan Reedy -- https

... (ellipsis)

I'm having understanding the use if the ellipsis. I keep reading that it is used in slices but every time I use it I get 'Syntax error' in 2.7 if 'Type error' in 3.2. In python2.7: l=range(15) l[...:11] Syntax error l[3:...] Syntax error l[3:...:11] Syntax error In python3.2 it becomes 'Type

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

Tim Peters added the comment: By the way, going back to your original problem, "the usual" solution to that different platforms can list directories in different orders is simply to sort the listing yourself. That's pretty easy in Python ;-) Then your test can verify the

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

Tim Peters <t...@python.org> added the comment: Jason, an ellipsis will match an empty string. But if your expected output is: """ x... abcd ... """ you're asking for output that: - starts with "x" - followed by 0 or more of anything - FOL

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

Jason R. Coombs <jar...@jaraco.com> added the comment: Thank you Steven for creating a reproduction of the issue; I should have done that in the first place. I have the +ELLIPSIS enabled elsewhere in the test suite, which is why it didn't appear in my example. I should clarify -

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

xample would then become: >>> print(res) # docstring: +ELLIPSIS d41d8cd98f00b204e9800998ecf8427e __init__.py ... check_output could replace the substring '' with three dots before doing anything else, and Bob's yer uncle. Or in this case, Uncle Timmy'

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

Tim Peters added the comment: And I somehow managed to unsubscribe Steven :-( -- nosy: +steven.daprano ___ Python tracker ___

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

alatable if you weren't determined to make it impenetrable ;-) For example, """ >>> print("not an ellipsis\\n" + res) #doctest:+ELLIPSIS not an ellipsis ... d41d8cd98f00b204e9800998ecf8427e __init__.py ... """ Or if this is a one-off, some suitab

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

Steven D'Aprano added the comment: Oops, somehow managed to accidentally unsubscribe r.david.murray -- nosy: +r.david.murray ___ Python tracker

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

Steven D'Aprano <steve+pyt...@pearwood.info> added the comment: Here's a simple demonstration of the issue: # --- cut %< --- import doctest def hash_files(): """ >>> hash_files() # doctest: +ELLIPSIS ... d41d8cd98f00b204e9800998ecf8427e __ini

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

R. David Murray added the comment: Ah, I see my answer crossed with your post :) -- ___ Python tracker ___

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

R. David Murray added the comment: What happens if you print a placeholder line first, before your test output? I'm not sure it will work, I seem to remember something about an ellipses starting a line just not being supported, but it was a long time ago... So, that

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

Jason R. Coombs added the comment: I did find [this ugly workaround](https://github.com/jaraco/jaraco.financial/commit/9b866ab7117d1cfc26d7cdcec10c63a608662b46): >>> print('x' + res) x... -- ___ Python tracker

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

) Expected: d41d8cd98f00b204e9800998ecf8427e __init__.py ... Got: e1f9390d13c90c7ed601afffd1b9a9f9 records.py 6a116973e8f29c923a08c2be69b11859 ledger.py d41d8cd98f00b204e9800998ecf8427e __init__.py b83c8a54d6b71e28ccb556a828e3fa5e qif.py ac2d598f65b6debe9888aafe51e9570f ofx.py

[issue31795] Slicings documentation doesn't mention Ellipsis

Raymond Hettinger <raymond.hettin...@gmail.com> added the comment: > Can we add an example of its usage in Numpy to the docs? I don't think we should. In CPython, the ellipsis has no interesting semantics. It is something that third-party modules can use however they wish. It doe

[issue31795] Slicings documentation doesn't mention Ellipsis

Nitish <nitishchandrachi...@gmail.com> added the comment: The problem is that while documentation for other objects like Null object, NotImplemented object make it clear what they are used for, documentation for Ellipsis object only says that it's used in slicings and the sl

[issue31795] Slicings documentation doesn't mention Ellipsis

Raymond Hettinger <raymond.hettin...@gmail.com> added the comment: In regular Python, the ellipsis isn't used for slicing. It does have special meaning for numpy. So, I think the docs may be correct as is. -- nosy: +rhettinger ___ Python t

[issue31795] Slicings documentation doesn't mention Ellipsis

New submission from Nitish <nitishchandrachi...@gmail.com>: Ellipsis object documentation[1] specifies that Ellipsis is mainly used by Slicings. But Slicing's documentation[2] doesn't mention anything about Ellipsis. Consequently - it is not immediately clear from Ellipsis documentatio

[issue31394] Ellipsis token.type != token.ELLIPSIS

Berker Peksag added the comment: If you look at https://docs.python.org/3/reference/lexical_analysis.html#delimiters '.' (period) is listed as delimiter and there is the following sentence to answer your question: A sequence of three periods has a special meaning as an ellipsis literal

[issue31394] Ellipsis token.type != token.ELLIPSIS

Aivar Annamaa added the comment: But it looks like Ellipsis is neither operator nor delimiter: https://docs.python.org/3/reference/lexical_analysis.html#operators -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/i

[issue31394] Ellipsis token.type != token.ELLIPSIS

type can be determined by checking the exact_type property on the named tuple returned from tokenize.tokenize(). If you replace the following line print(ellipsis) with print(ellipsis.exact_type) you will see that it prints '52'. -- nosy: +berker.peksag resolution

[issue31394] Ellipsis token.type != token.ELLIPSIS

New submission from Aivar Annamaa: Type code for ellipsis token doesn't match with the constant token.ELLIPSIS: --- import io import token import tokenize source = "..." tokens = list(tokenize.tokenize(io.BytesIO(source.encode('utf-8')).readline)

[issue29356] TypeError by typing for Ellipsis

Ádám Szieberth added the comment: Well, now I believe the way I suggested would conflict with other uses of Ellipsis in type hints. -- resolution: -> not a bug status: open -> closed ___ Python tracker <rep...@bugs.python.o

[issue29356] TypeError by typing for Ellipsis

New submission from Ádám Szieberth: I would expect Ellipsis the same behavior as None in type hints instead of: TypeError: Union[arg, ...]: each arg must be a type. Got Ellipsis. ... would be much nicer than type(...) there. -- messages: 286134 nosy: Ádám Szieberth priority: normal

[issue22144] ellipsis needs better display in lexer documentation

R. David Murray added the comment: I agree that there is nothing to do here. The ... does not belong in the table, since as Martin says it is a literal, not a delimiter. In theory you could create a whole new section named 'elipsis literal' above the delmiiters section, but that hardly

[issue22144] ellipsis needs better display in lexer documentation

New submission from François-René Rideau: As a followup to http://bugs.python.org/issue21972 The ellipsis (three dots) should be displayed in the box on top of section 2.6 of the reference manual, and not just in the text below: https://docs.python.org/3.5/reference/lexical_analysis.html

[issue22144] ellipsis needs better display in lexer documentation

Martin v. Löwis added the comment: I don't think that ... is a delimiter. Instead, it is a literal of the ellipsis class. -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22144

[issue21103] Encoding str to IDNA with ellipsis decomposes to empty labels

string ends with U+2026 HORIZONTAL ELLIPSIS if you can't see it clearly. These strings are coming from web pages in a web crawler. I tested this on Python 3.4, 3.3.2, 2.7.5, 2.6.9. -- components: Library (Lib) messages: 215189 nosy: chfoo priority: normal severity: normal status: open

[issue21103] Encoding str to IDNA with ellipsis decomposes to empty labels

Martin v. Löwis added the comment: I believe this behavior is correct wrt. RFC 3490. In the input, the last label is c…, which is not empty. It is passed to ToASCII, which normalizes the ellipsis to If UseSTD3ASCIIRules was true, conversion would fail as it yields . (\x2E). However

[issue21103] Encoding str to IDNA with ellipsis decomposes to empty labels

R. David Murray added the comment: For whatever it is worth, it looks like rfc 5892 marks U+2026 as disallowed. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21103

Re: proposal: Ellipsis in argument list

On Sat, Jan 12, 2013 at 5:30 AM, Szabolcs Blága szabolcs.bl...@gmail.comwrote: Dear All, I have an idea that the Ellipsis object could be used in function calls. The ... syntax should automagically turn into an Ellipsis positional argument. def f(*args): ext_args = [] for i

proposal: Ellipsis in argument list

Dear All, I have an idea that the Ellipsis object could be used in function calls. The ... syntax should automagically turn into an Ellipsis positional argument. def f(*args): ext_args = [] for i, a in enumerate(args): if a is Ellipsis: ext_args.extend([x for x in range(args[i-1]-1

Re: proposal: Ellipsis in argument list

Szabolcs Blága, 12.01.2013 14:30: I have an idea that the Ellipsis object could be used in function calls. The ... syntax should automagically turn into an Ellipsis positional argument. def f(*args): ext_args = [] for i, a in enumerate(args): if a is Ellipsis

[issue14741] parser module doesn't support Ellipsis.

: parser_ellipsis.patch keywords: patch messages: 160157 nosy: mark.dickinson priority: normal severity: normal stage: needs patch status: open title: parser module doesn't support Ellipsis. type: behavior versions: Python 3.2, Python 3.3 Added file: http://bugs.python.org/file25487/parser_ellipsis.patch

[issue14741] parser module doesn't support Ellipsis.

Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 2b1cc84bf1d9 by Mark Dickinson in branch '3.2': Issue #14741: Fix missing support for ellipsis in parser module. http://hg.python.org/cpython/rev/2b1cc84bf1d9 New changeset d50577c5711b by Mark Dickinson in branch

[issue14741] parser module doesn't support Ellipsis.

Changes by Mark Dickinson dicki...@gmail.com: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14741 ___

[issue13842] Cannot pickle Ellipsis or NotImplemented

Łukasz Langa luk...@langa.pl added the comment: There is indeed a 5% performance gain from using PyUnicode_FromString instead of the generic Py_BuildValue function. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13842

[issue13842] Cannot pickle Ellipsis or NotImplemented

Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 5832d3622473 by Łukasz Langa in branch 'default': Fixes #13842: cannot pickle Ellipsis or NotImplemented. http://hg.python.org/cpython/rev/5832d3622473 -- nosy: +python-dev

[issue13842] Cannot pickle Ellipsis or NotImplemented

Changes by Łukasz Langa luk...@langa.pl: -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13842 ___

[issue13842] Cannot pickle Ellipsis or NotImplemented

Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 5353357382e2 by Łukasz Langa in branch 'default': #13842: check whether PyUnicode_FromString succeeded http://hg.python.org/cpython/rev/5353357382e2 -- ___ Python tracker

[issue13842] Cannot pickle Ellipsis or NotImplemented

Changes by Łukasz Langa luk...@langa.pl: -- assignee: - lukasz.langa nosy: +lukasz.langa ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13842 ___

[issue13842] Cannot pickle Ellipsis or NotImplemented

Antoine Pitrou pit...@free.fr added the comment: I haven't taken a look at the patch in detail, but it lacks some tests. Pickling tests are generally in Lib/test/pickletester.py, they are invoked by test_pickle and test_pickletools. -- stage: needs patch - patch review

[issue13842] Cannot pickle Ellipsis or NotImplemented

Changes by Antoine Pitrou pit...@free.fr: -- nosy: +hynek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13842 ___ ___ Python-bugs-list mailing

[issue13842] Cannot pickle Ellipsis or NotImplemented

Antoine Pitrou pit...@free.fr added the comment: I'm completely new to the C API so not sure if the way I am building python strings (to pass to save_global) is correct It's correct but it's probably less efficient than calling a more specialized function, such as PyUnicode_FromString():

[issue13842] Cannot pickle Ellipsis or NotImplemented

James Sanders bistromath...@gmail.com added the comment: I've submitted a patch that just uses save_global to pickle Ellipsis and NotImplemented, so the resulting pickle should be unpicklable anywhere. I'm completely new to the C API so not sure if the way I am building python strings

[issue13842] Cannot pickle Ellipsis or NotImplemented

New submission from James Sanders bistromath...@gmail.com: At present, the built-in constants Ellipsis (...) and NotImplemented cannot be pickled. Perhaps there is a good reason for this, but the only discussion I can find is at msg108957, where it is stated that these values (along

[issue13842] Cannot pickle Ellipsis or NotImplemented

Antoine Pitrou pit...@free.fr added the comment: I think it's a reasonable feature request. Now someone has to write a patch for it. -- stage: - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13842

[issue13842] Cannot pickle Ellipsis or NotImplemented

Alexandre Vassalotti alexan...@peadrop.com added the comment: We will need to bump the protocol number to add support for None, Ellipsis, and NotImplemented. Antoine, can you add this to PEP 3154? -- ___ Python tracker rep...@bugs.python.org http

[issue13842] Cannot pickle Ellipsis or NotImplemented

Antoine Pitrou pit...@free.fr added the comment: We will need to bump the protocol number to add support for None, Ellipsis, and NotImplemented. Antoine, can you add this to PEP 3154? I don't think this needs a protocol bump. These are global singletons, they can be pickled

Python Pickle Problems (Ellipsis + Other Objects)

See more details in my forum post: http://www.python-forum.org/pythonforum/viewtopic.php?f=18t=26724 I'm trying to pickle a bunch of functions (mostly built-in) and pickle keeps giving me errors. I have no Ellipsis in my data at all, and for some reason, pickle seems to think I do. Here

[issue12056] … (HORIZONTAL ELLIPSIS) should be an alternative syntax for ... (FULL STOP FULL STOP FULL STOP)

New submission from Xavier Morel xavier.mo...@masklinn.net: In Python 3, ... became useable as a normal expression, and translates into an ellipsis instance. Unicode defines an ellipsis character … (U+2026 HORIZONTAL ELLIPSIS) which is canonically equivalent to a 3-sequence of FULL STOP [U

[issue12056] … (HORIZONTAL ELLIPSIS) should be an alternative syntax for ... (FULL STOP FULL STOP FULL STOP)

Changes by Antoine Pitrou pit...@free.fr: -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12056 ___ ___ Python-bugs-list

[issue12056] … (HORIZONTAL ELLIPSIS) should be an alternative syntax for ... (FULL STOP FULL STOP FULL STOP)

Brandon Craig Rhodes bran...@rhodesmill.org added the comment: But if we allow for ellipsis, then would we not also have to start allowing characters like ≥ and ≤ in Python? And the problem with any of these (admittedly very attractive) substitutions is that they seem to abandon the principle

  1   2   >