[issue15003] make PyNamespace_New() public

2021-05-12 Thread STINNER Victor
Change by STINNER Victor : -- nosy: -vstinner resolution: -> rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue15003] make PyNamespace_New() public

2021-05-12 Thread Jouke Witteveen
Change by Jouke Witteveen : -- nosy: +joukewitteveen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue15003] make PyNamespace_New() public

2013-02-16 Thread Eric Snow
Eric Snow added the comment: At present, I don't see a need to make the C API public. -- status: open -> closed ___ Python tracker ___ ___

[issue15003] make PyNamespace_New() public

2012-07-02 Thread Éric Araujo
Éric Araujo added the comment: Suggest closing or marking “remind” and see if people use / request / reimplement SimpleNamespace. -- versions: +Python 3.4 -Python 3.3 ___ Python tracker __

[issue15003] make PyNamespace_New() public

2012-06-24 Thread Mark Shannon
Mark Shannon added the comment: -1 for the reasons Nick stated. -- nosy: +Mark.Shannon ___ Python tracker ___ ___ Python-bugs-list ma

[issue15003] make PyNamespace_New() public

2012-06-24 Thread Nick Coghlan
Nick Coghlan added the comment: -1. The entire Python API is already accessible from C, so expansions to the public C API need more justification than "it's exposed in Python". If new instances of this type end up being used in performance critical third party C extensions, then we can have a

[issue15003] make PyNamespace_New() public

2012-06-23 Thread Eric Snow
Changes by Eric Snow : Removed file: http://bugs.python.org/file25853/issue15003_public.diff ___ Python tracker ___ ___ Python-bugs-list maili

[issue15003] make PyNamespace_New() public

2012-06-23 Thread Eric Snow
Eric Snow added the comment: Here's an updated patch to address the use of _PyNamespace_New() in changeset 77414:0011536f2a06. -- Added file: http://bugs.python.org/file26119/issue15003_public.diff ___ Python tracker

[issue15003] make PyNamespace_New() public

2012-06-12 Thread Éric Araujo
Éric Araujo added the comment: >> Is this documented in whatsnew? > I'm not sure what has been (none of my patches have done so). Okay; if a committer does not add a note we can open a doc bug to not forget that. >> Also, I remember a discussion about making it public or not, but >> don’t reca

[issue15003] make PyNamespace_New() public

2012-06-11 Thread Eric Snow
Eric Snow added the comment: > Is this documented in whatsnew? I'm not sure what has been (none of my patches have done so). > Also, I remember a discussion about making it public or not, but > don’t recall a decision. Amaury brought it up in msg162127. His point was that the type is public

[issue15003] make PyNamespace_New() public

2012-06-09 Thread Éric Araujo
Éric Araujo added the comment: > The type is available as types.SimpleNamespace (sorry for being OT) Is this documented in whatsnew? Also, I remember a discussion about making it public or not, but don’t recall a decision. I personally find it bad that we have structseqs for most things, di

[issue15003] make PyNamespace_New() public

2012-06-07 Thread Eric Snow
Changes by Eric Snow : -- stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue15003] make PyNamespace_New() public

2012-06-06 Thread Eric Snow
Eric Snow added the comment: I've opened issue 15022 for making SimpleNamespace picklable. -- ___ Python tracker ___ ___ Python-bugs-

[issue15003] make PyNamespace_New() public

2012-06-06 Thread Eric Snow
Eric Snow added the comment: Where should the docs go for PyNamespace_New()? I looked at what's in Doc/c-api/concrete.rst (concrete.html#other-objects), and each of them points to its own page. Adding a new page for a single function seems a bit too much. :) Would it be bad to put the doc

[issue15003] make PyNamespace_New() public

2012-06-06 Thread Eric Snow
Changes by Eric Snow : Removed file: http://bugs.python.org/file25827/issue15003_public.diff ___ Python tracker ___ ___ Python-bugs-list maili

[issue15003] make PyNamespace_New() public

2012-06-06 Thread STINNER Victor
STINNER Victor added the comment: It would be nice to have a minimum documentation :-) What is the kwds parameter? What are attributes of the object? -- nosy: +haypo ___ Python tracker ___

[issue15003] make PyNamespace_New() public

2012-06-05 Thread Eric Snow
Eric Snow added the comment: I'll get to a pickle patch as soon as I can. I also need to add a doc addition for PyNamespace_New() to the existing patch. -- ___ Python tracker

[issue15003] make PyNamespace_New() public

2012-06-04 Thread Eric Snow
Eric Snow added the comment: I'll get a patch up tomorrow to make the type pickleable. -- ___ Python tracker ___ ___ Python-bugs-list

[issue15003] make PyNamespace_New() public

2012-06-04 Thread Eric Snow
Eric Snow added the comment: Patch to make PyNamespace_New() public. -- keywords: +patch Added file: http://bugs.python.org/file25827/issue15003_public.diff ___ Python tracker _

[issue15003] make PyNamespace_New() public

2012-06-04 Thread Raymond Hettinger
Raymond Hettinger added the comment: SimpleNamespaces also need to be picklable. -- nosy: +rhettinger ___ Python tracker ___ ___ Pyth

[issue15003] make PyNamespace_New() public

2012-06-04 Thread Eric Snow
New submission from Eric Snow : The type is available as types.SimpleNamespace, and there's no reason to hold PyNamespace_New() back. -- components: Library (Lib) messages: 162322 nosy: amaury.forgeotdarc, eric.snow priority: normal severity: normal stage: needs patch status: open title