[issue16932] urlparse fails at parsing "www.python.org:80/"
Sandro Tosi added the comment: The documentation reports this example: >>> urlparse('www.cwi.nl:80/%7Eguido/Python.html') ParseResult(scheme='', netloc='', path='www.cwi.nl:80/%7Eguido/Python.html', params='', query='', fragment='') but when executing it returns: $ ./python -V Python 2.7.3+ $ ./python -c "from urlparse import urlparse ; print urlparse('www.cwi.nl:80/%7Eguido/Python.html')" ParseResult(scheme='www.cwi.nl', netloc='', path='80/%7Eguido/Python.html', params='', query='', fragment='') which doesn't match. -- ___ Python tracker <http://bugs.python.org/issue16932> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16932] urlparse fails at parsing "www.python.org:80/"
Sandro Tosi added the comment: Adding Senthil as per expert list -- nosy: +orsenthil ___ Python tracker <http://bugs.python.org/issue16932> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16932] urlparse fails at parsing "www.python.org:80/"
New submission from Sandro Tosi: Hello, as reported at http://mail.python.org/pipermail/docs/2013-January/012375.html urlparse fails to parse URLs without a schema and with a url path, as opposed to what's documented at http://docs.python.org/2/library/urlparse.html?highlight=urlparse#urlparse : ./python -c "from urlparse import urlparse ; print(urlparse('python.org:80/'))" ParseResult(scheme='python.org', netloc='', path='80/', params='', query='', fragment='') (that is for 2.7, but the same happens on all the 3.x active branches). i'm attaching a test to expose this failure. -- components: Library (Lib) files: urlparse.diff keywords: patch messages: 179670 nosy: sandro.tosi priority: normal severity: normal stage: needs patch status: open title: urlparse fails at parsing "www.python.org:80/" versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4 Added file: http://bugs.python.org/file28692/urlparse.diff ___ Python tracker <http://bugs.python.org/issue16932> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16813] use paths relative to CPython root in documentation building instructions
Sandro Tosi added the comment: > Out of curiosity, does anyone know if the following works on all or most > systems? > > $ open _build/html/index.html it doesn't work on my Debian system: $ open _build/html/index.html Couldn't get a file descriptor referring to the console as open is a link to "openvt - start a program on a new virtual terminal (VT)." -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue16813> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16814] use --directory option of make
Sandro Tosi added the comment: i'd use make -C Doc html much more compact and what you would usually find on the internet for "cd into the dir and run the html target in it" -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue16814> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16805] when building docs on Debian 7 --> ERROR: Error in "note" directive
Sandro Tosi added the comment: On Sat, Dec 29, 2012 at 4:07 PM, Tshepang Lekhonkhobe wrote: >> no-one has done the work of testing, preparation and migration: do you >> volunteer? :) > > What needs doing exactly? I would volunteer if guided. I normally (you always can't expect to be guided) it's not much more than - update sphinx (and the other tools it depends on, if needed). - fix what's broken or what needs updating - verify the doc is ok for any supported branches. > Also, can I submit a patch that adds the missing newlines, or will > some committer take care of it, or does this need further discussion? it won't hurt to have a patch. But please build the doc it with the CPython selected tools before submitting the patch, and verifying the doc sections you've changed are still ok. -- ___ Python tracker <http://bugs.python.org/issue16805> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16805] when building docs on Debian 7 --> ERROR: Error in "note" directive
Sandro Tosi added the comment: On Sat, Dec 29, 2012 at 4:33 AM, Tshepang Lekhonkhobe wrote: > It is my preference to be able to build all of CPython with the > already-installed distro packages, instead of pulling in foreign ones. IMO, I think with a project as bit as CPython, you should leave you personal preferences apart and use (as much as possible) the tools the project has decided to use: having a consistent set of tools to build doc across everyone/everything (like auto-build doc machines) trying to generate the doc is the proper way to handle it. > Any reason why not use later versions? no-one has done the work of testing, preparation and migration: do you volunteer? :) > Can't the docs be written such > that they can run on various versions of these tools anyway? Not always, but of course, as Georg said, if for note directive we can have a syntax working with current and higher versions of sphinx/docutils, that's ok to do it. I only think that using a non-standard set of doc-build-tools is to be discouraged, and sticking to what Makefile will fetch is the proper way to build the doc and contribute to it. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- ___ Python tracker <http://bugs.python.org/issue16805> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16805] when building docs on Debian 7 --> ERROR: Error in "note" directive
Sandro Tosi added the comment: Hello Tshepang, the documentation is not compatible with Sphinx versions different than the one the Makefile will download (in this case it's 1.0.7 for all active branches). I'd suggest to build the doc with just $ make -C Doc html and it will fetch the needed modules (at the correct version) and build the html version of the documentation in Doc/build/html/. I'm inclined to close this issue as invalid, but I'd like to hear from your first. Regards, Sandro -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue16805> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Sandro Tosi added the comment: I think the aim of that part of the devguide is to give one clear, simple, working way to operate on different branches at the same time. Additional workflows can be presented, but probably in another place (like the FAQ indeed). What others thing about this? -- ___ Python tracker <http://bugs.python.org/issue14468> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12415] Missing: How to checkout the Doc sources
Sandro Tosi added the comment: Éric: I've just committed your patch, with also the latest changes. Philip: In order to be consistent with the way the documentation is compiled on the Python platform, the svn checkout must be used: else if you refer to the upstream website, a contributor can checkout an updated version that will generate a different result. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue12415> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Sandro Tosi added the comment: Hi Ezio, thanks for the review: how about this new version of the patch? I've left the more "verbose" version in the 3.2 example, while used the more compact way for the 2.7 . Re first committing to 2.7 then 3.2 and then merge, that would work for doc patches, but probably what happens most of the time is the commit in 3.2 and merge on default, which should be covered. Any other comments? -- Added file: http://bugs.python.org/file26937/issue14468-v2.diff ___ Python tracker <http://bugs.python.org/issue14468> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13799] Base 16 should be hexadecimal in Unicode HOWTO
Sandro Tosi added the comment: I tend to agree with Terry that this report can be closed: base 16 is quite known and it's high likely that if you know what hexadecimal is, you also aware of the concept of "base X" and viceversa. If no-one objects, I'd just close it. -- ___ Python tracker <http://bugs.python.org/issue13799> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15677] Gzip/zlib allows for compression level=0
New submission from Sandro Tosi: As reported at http://mail.python.org/pipermail/docs/2012-August/009837.html gzip/zlib allows for a compression level=0 (that's basically no compression) so the documentation should mention that possibility too. -- assignee: docs@python components: Documentation messages: 168332 nosy: docs@python, sandro.tosi priority: normal severity: normal stage: needs patch status: open title: Gzip/zlib allows for compression level=0 versions: Python 2.7, Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue15677> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15656] "Extending Python with C" page needs update for 3.x
Sandro Tosi added the comment: It's fixed in default too: http://hg.python.org/cpython/rev/f46b4b7b817c It was not shown because the commit message misses the issue reference. -- ___ Python tracker <http://bugs.python.org/issue15656> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15657] Error in Python 3 docs for PyMethodDef
New submission from Sandro Tosi: Hello, it has been reported at http://mail.python.org/pipermail/docs/2012-April/008215.html but given it raises some question whether it's a bug in the doc or in the code, i'd rather report the issue here and hear what other think: >>> In the Python 3.2.2 documentation (and earlier Python 3 versions), in the Python/C API Reference Manual, chapter Object Implementation Support, the documentation for PyMethodDef says: The ml_flags field is a bitfield which can include the following flags. The individual flags indicate either a calling convention or a binding convention. Of the calling convention flags, only METH_VARARGS and METH_KEYWORDS can be combined (but note that METH_KEYWORDS alone is equivalent to METH_VARARGS | METH_KEYWORDS). The bit in the parenthetical is incorrect. If you take a look at PyCFunction_Call in Objects/methodobject.c, you will find a switch for METH_VARARGS | METH_KEYWORDS, but no switch for METH_KEYWORDS. Hence, using METH_KEYWORDS will land you with a SystemError that complains about METH_OLDARGS. This is either a bug in the documentation, or a bug in Python. In this case, since the code has persisted through three major revisions of Python 3, I suggest that the bug _is_ in the documentation (whether it should be or not), since changing the code for this at this late date means a programmer has to use METH_VARARGS | METH_KEYWORDS anyway for compatibility. It may be work pointing out specifically in the documentation that just using METH_KEYWORDS will not work. <<< -- assignee: docs@python components: Documentation messages: 168226 nosy: docs@python, sandro.tosi priority: normal severity: normal stage: patch review status: open title: Error in Python 3 docs for PyMethodDef versions: Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue15657> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15656] "Extending Python with C" page needs update for 3.x
New submission from Sandro Tosi: Hello, this has been reported at http://mail.python.org/pipermail/docs/2012-July/009223.html but since I have no experience to judge if it's correct or not, i'll just report it: >>> I've recenty started to try using C code in python using the wonderful python API, although i have to say the learning curve was non neglectable :P I've spotted what I believe to be a small mistake in the documentation from this page: http://docs.python.org/release/3.2/extending/extending.html In paragraph 1.8 (http://docs.python.org/release/3.2/extending/extending.html#keyword-parameters-for-extension-functions), the code example given contains an error, which is actually obsolete code from python 2.7: void initkeywdarg(void) { /* Create the module and add the functions */ Py_InitModule("keywdarg", keywdarg_methods); } This doesn't work in Python3.2. It's supposed to be static struct PyModuleDef keywdargmodule = { PyModuleDef_HEAD_INIT, "keywdarg", /* name of module */ keywdarg_doc, /* module documentation, may be NULL */ -1, /* size of per-interpreter state of the module, or -1 if the module keeps state in global variables. */ keywdarg_methods }; PyMODINIT_FUNC PyInit_keywdarg(void) { return PyModule_Create(&keywdargmodule); } As explained above (and confirmed by experience). <<< -- assignee: docs@python components: Documentation messages: 168223 nosy: docs@python, sandro.tosi priority: normal severity: normal stage: patch review status: open title: "Extending Python with C" page needs update for 3.x versions: Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue15656> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15060] docs: socket typo
Sandro Tosi added the comment: Thanks! -- nosy: +sandro.tosi resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: +Python 2.7, Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue15060> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15014] smtplib: allow to choose auth method on login()
New submission from Sandro Tosi : Hello, I'm writing some tests from an MTA, and so I'm using smtplib. Sadly the login() method doesn't allow to choose the auth method to use (but it's selected from a static list compared with what's advertized from the MTA) while it would be useful to be able to choose the AUTH method to use. -- components: Library (Lib) messages: 162396 nosy: sandro.tosi priority: normal severity: normal status: open title: smtplib: allow to choose auth method on login() versions: Python 3.3 ___ Python tracker <http://bugs.python.org/issue15014> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15013] smtplib: add low-level APIs to doc?
New submission from Sandro Tosi : In the smtplib doc I read: Low-level methods corresponding to the standard SMTP/ESMTP commands HELP, RSET, NOOP, MAIL, RCPT, and DATA are also supported. Normally these do not need to be called directly, so they are not documented here. For details, consult the module code. Well, I think the documentation should include also those low-level apis (maybe in a separate subsection). >From my POV, smtplib should implement the protocol, and give the programmers >the tools to use the protocol as they prefers, and as a plus some companion >methods to easy the most common operations. I'm in need to use the low-level apis, and not finding them in the doc is a disservice to me (with my user hat on ;)) and just say "go read the source" is kinda rude and unexpected. What do you think? -- assignee: docs@python components: Documentation messages: 162395 nosy: docs@python, sandro.tosi priority: normal severity: normal stage: needs patch status: open title: smtplib: add low-level APIs to doc? versions: Python 2.7, Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue15013> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14926] random.seed docstring needs edit of "*a *is"
Sandro Tosi added the comment: Thanks Christopher! -- resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: -Python 2.7 ___ Python tracker <http://bugs.python.org/issue14926> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14814] Implement PEP 3144 (the ipaddress module)
Sandro Tosi added the comment: and the patch... -- Added file: http://bugs.python.org/file25800/ipaddress_module_doc.diff ___ Python tracker <http://bugs.python.org/issue14814> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14814] Implement PEP 3144 (the ipaddress module)
Sandro Tosi added the comment: Attached is a draft of the module documentation. I didn't commit yet cause we might want to rework it deeply. Else we can just commit the patch and let the comments coming as additional diffs. -- stage: needs patch -> patch review ___ Python tracker <http://bugs.python.org/issue14814> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14968] Section "Inplace Operators" of :mod:`operator` should be a subsection
Sandro Tosi added the comment: Thanks Lars for the patch! Éric, why did you add 2.7 version? AFAISee 2.7 doesn't have the "Inplace Operators" section. -- ___ Python tracker <http://bugs.python.org/issue14968> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14814] Implement PEP 3144 (the ipaddress module)
Sandro Tosi added the comment: Thanks Hynek: comments committed -- ___ Python tracker <http://bugs.python.org/issue14814> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14814] Implement PEP 3144 (the ipaddress module)
Sandro Tosi added the comment: Thank Nick for pointing to Terry's review! I'm attaching here a patch addressing the points Terry highlighed. probably we should review this patch before moving forward with the API doc? -- Added file: http://bugs.python.org/file25675/ipaddress_improvements.diff ___ Python tracker <http://bugs.python.org/issue14814> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14814] Implement PEP 3144 (the ipaddress module)
Sandro Tosi added the comment: I'm attaching a very preliminary draft of the howto, any comment is welcome. Of course, it misses several references to the API doc; I'll see if I can beat Georg and post a preliminary version of that too :) -- keywords: +patch nosy: +sandro.tosi Added file: http://bugs.python.org/file25654/issue14814-ipaddress-howto.diff ___ Python tracker <http://bugs.python.org/issue14814> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12947] doctest directive examples in library/doctest.html lack the flags
Changes by Sandro Tosi : -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue12947> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14865] #doctest: directives removed from doctest chapter examples
Sandro Tosi added the comment: Hi Terry, the same problem recently came up on docs@ and digging into it, it turned out that sphinx is currently ignoring doctest directives[1], but that it was fixed in sphinx 1.1[2]. [1] https://bitbucket.org/birkenfeld/sphinx/issue/169/strip-doctest-csomments-in-rendered-output [2] https://bitbucket.org/birkenfeld/sphinx/changeset/d91bf8e465ef It's likely the bug is visible on the active branches because recently they were updated to use the same sphinx version. We can probably plan to update the sphinx we use for the doc - what do you think about it? -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue14865> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14793] broken grammar in Built-in Types doc
Sandro Tosi added the comment: I think that something on the line "Hey, it looks like this phrase misses some words, and I've just fixed it" would have been nicer - IMO. -- ___ Python tracker <http://bugs.python.org/issue14793> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14793] broken grammar in Built-in Types doc
Sandro Tosi added the comment: Committed, thanks for the patch. For next times, please invest even a small amount of time describing why you opened the issue and what the patch fixes: it's definitely nicer not having to infer it from the diff. -- nosy: +sandro.tosi resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue14793> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14187] add "function annotation" entry to Glossary
Sandro Tosi added the comment: I agree with Raymond that last paragraph should be removed; +1 for the remaining part -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue14187> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12298] Sphinx glitch in library/functions
Sandro Tosi added the comment: Oh sorry Éric, I completely oversaw there was an issue associated with the cset - i'll pay more attention next time! -- ___ Python tracker <http://bugs.python.org/issue12298> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Sandro Tosi added the comment: Here's the proposed patch. I'm sorry but probably 'hg diff' went too wild, and since I moved the "Using several working copies" as the first sub-paragraph of "Forward-Porting" it seems it got confused, so the diff is not so clean. I've also changed quite some part of "Porting Within *" sections - please look at them carefully since it's not that evident. A brief list is: - change in commands to reflect the multi-clone setup - add of "Assuming all your clones are in the same directory" - add of "The import is possible..." sentence -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file25458/issue14468.diff ___ Python tracker <http://bugs.python.org/issue14468> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Sandro Tosi added the comment: +1 It is important to note that if you have a 'cpython' as a clone (which pulls and pushed to hg.python.org) and from it you clone '2.7' and '3.2' (as I think it's the most common setup) you first have to pull from cpython and then on the other 2. Anyhow, is anyone up for preparing a patch? else I'll happily work on it in the coming days. -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue14468> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14691] a code example not highlighted in http://docs.python.org/dev/library/stdtypes.html#memoryview
Sandro Tosi added the comment: It's seems like a deja-vu: I thought I saw this problem once, and was already fixed - bah, it was tricky (traceback needs to be indented for the code to be highlighted), that's why I remember it -- nosy: +sandro.tosi resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue14691> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14676] DeprecationWarning missing in default warning filters documentation
Sandro Tosi added the comment: Peter: thanks for the patch! -- nosy: +sandro.tosi resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue14676> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14448] Mention pytz in datetime's docs
Sandro Tosi added the comment: I've reworded a bit the patch: thanks for it, Andrew -- nosy: +sandro.tosi resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue14448> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14554] test module: correction
Sandro Tosi added the comment: Thanks for the patch, Tshepang! -- nosy: +sandro.tosi resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue14554> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13478] No documentation for timeit.default_timer
Changes by Sandro Tosi : -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue13478> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13587] Correcting the typos error in Doc/howto/urllib2.rst
Sandro Tosi added the comment: Aaron: thanks for the patch! -- nosy: +sandro.tosi resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue13587> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13934] sqlite3 test typo
Sandro Tosi added the comment: poq, would you like to also prepare a patch for the documentation with what Thomas suggested? I'd be happy to review when ready -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue13934> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14650] 1-character typo in shutil docstring
Sandro Tosi added the comment: Thanks for your contribution! -- nosy: +sandro.tosi resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue14650> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14641] Minor fixes in sockets.rst
Sandro Tosi added the comment: Thanks for your contribution! -- nosy: +sandro.tosi resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: +Python 3.2 ___ Python tracker <http://bugs.python.org/issue14641> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14502] Document better what happens on releasing an unacquired lock
Changes by Sandro Tosi : -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue14502> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14502] Document better what happens on releasing an unacquired lock
Sandro Tosi added the comment: On Thu, Apr 5, 2012 at 09:06, Georg Brandl wrote: > I agree: if we know that a ThreadError will always be raised in this > instance, we should document it as such. I've already prepared a small patch for that (every supported release has a different exception raised..) I'll be fixing it this evening at home. -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue14502> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Sandro Tosi added the comment: I've just uploaded regex into Debian: this will hopefully gives some more eyes looking at the module and reporting some feedbacks. -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue2636> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14316] Broken link in grammar.rst
Changes by Sandro Tosi : -- nosy: +sandro.tosi resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue14316> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14410] argparse typo
Sandro Tosi added the comment: Thanks for your patch: committed! -- nosy: +sandro.tosi resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue14410> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14218] include rendered output in addition to markup
Sandro Tosi added the comment: eheh yeah it seems so :) What I think Tshepang wants is this: - the devguide contains the description of how to document python - that documentation is about a set of ReST coding commands that generate the desired output - currently the devguide reports only the ReST code block without, right below to that block, the resulting highlitening. -> add the resulting "visual" output right below the description of the code to use. so something like blablabla you have to use ``word`` to have the word in bold (or whatever it generates, I'm too lazy to check :) ) for example: Tshepang: did I get it correctly? Éric: is it (at least a bit) clearer? -- ___ Python tracker <http://bugs.python.org/issue14218> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14219] start the Class tutorial in a more gentle manner
Sandro Tosi added the comment: see msg155067 -- nosy: +sandro.tosi versions: -Python 2.6, Python 3.1 ___ Python tracker <http://bugs.python.org/issue14219> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14218] include rendered output in addition to markup
Sandro Tosi added the comment: additionally, devguide has no version associated with it. -- versions: -Python 2.7, Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue14218> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14218] include rendered output in addition to markup
Sandro Tosi added the comment: 3.1 and 2.6 as in security fix only: please don't add those versions for non-sec issue -- nosy: +sandro.tosi versions: -Python 2.6, Python 3.1 ___ Python tracker <http://bugs.python.org/issue14218> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2403] Add figleaf coverage metrics
Sandro Tosi added the comment: The devguide reports a long section about code convering cpython: http://docs.python.org/devguide/coverage.html . It uses Ned's coverege.py and has a lot of details about how to use it and how to generate nice reports out of it. do we need an internal tool for cpython coverage? -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue2403> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13999] Queue references in multiprocessing doc points to Queue module and not to self
Changes by Sandro Tosi : -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue13999> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13605] document argparse's nargs=REMAINDER
Sandro Tosi added the comment: On Mon, Feb 20, 2012 at 01:52, Éric Araujo wrote: > I’m not entirely sure they are needed (Python code blocks seem to be > autodetected and show up colorized too), but I did it for consistency (and to > make my editor detect them). Yeah, I refrained to add them since the code blocks were already correctly identified; but consistency is Good :) -- ___ Python tracker <http://bugs.python.org/issue13605> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14050] Tutorial, list.sort() and items comparability
Changes by Sandro Tosi : Added file: http://bugs.python.org/file24558/list_sort-py32.diff ___ Python tracker <http://bugs.python.org/issue14050> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14050] Tutorial, list.sort() and items comparability
New submission from Sandro Tosi : I'm providing patches for what reported at http://mail.python.org/pipermail/docs/2012-February/007481.html . I'm not sure on wording or even if we want them in the tutorial section, but I think it would be nice to have it documented nonetheless. -- assignee: docs@python components: Documentation files: list_sort-py27.diff keywords: patch messages: 153648 nosy: docs@python, sandro.tosi priority: normal severity: normal stage: patch review status: open title: Tutorial, list.sort() and items comparability versions: Python 2.7, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file24557/list_sort-py27.diff ___ Python tracker <http://bugs.python.org/issue14050> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11836] multiprocessing.queues.SimpleQueue is undocumented
Sandro Tosi added the comment: Thanks for all you inputs! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue11836> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11836] multiprocessing.queues.SimpleQueue is undocumented
Sandro Tosi added the comment: >> OK, so if I got it correctly, I should document >> multiprocessing.queue.SimpleQueue in 2.7 and 3.1 [...] > > s/3.1/3.2/ yeah, just a typo :) -- ___ Python tracker <http://bugs.python.org/issue11836> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11836] multiprocessing.queues.SimpleQueue is undocumented
Sandro Tosi added the comment: It's the way all the subclasses are imported into the main module that got me in fault, I think. OK, so if I got it correctly, I should document multiprocessing.queue.SimpleQueue in 2.7 and 3.1 and multiprocessing.SimpleQueue in 3.3 also adding the hunk to __init__ (thus changing the API). I'd say to document int still near to Queue() and JoinableQueue() - do you agree? -- ___ Python tracker <http://bugs.python.org/issue11836> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13999] Queue references in multiprocessing doc points to Queue module and not to self
New submission from Sandro Tosi : At the subject says, several references to Queue are linking to Queue module and not to multiprocessing. -- assignee: docs@python components: Documentation messages: 153218 nosy: docs@python, sandro.tosi priority: normal severity: normal stage: needs patch status: open title: Queue references in multiprocessing doc points to Queue module and not to self versions: Python 2.7, Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue13999> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11836] multiprocessing.queues.SimpleQueue is undocumented
Sandro Tosi added the comment: Thanks Eli for the heads-up, I had missed Antoine's comment! Antoine, I'm probably missing something, but SimpleQueue is present in 2.7 and 3.2 too, so why not mention it in the doc for those versions too? -- ___ Python tracker <http://bugs.python.org/issue11836> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13939] excessive cpu usage
Changes by Sandro Tosi : -- components: -None versions: -Python 2.7 ___ Python tracker <http://bugs.python.org/issue13939> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13939] excessive cpu usage
Sandro Tosi added the comment: Hello, i'm sorry but this is not the right place for this report. Please refer to ubuntu or gnome user support forum for help. Sandro -- nosy: +sandro.tosi resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue13939> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13868] Add hyphen doc fix
Sandro Tosi added the comment: On Wed, Feb 1, 2012 at 15:42, Boštjan Mejak wrote: > Seriously, how old are you two clowns? I think it's enough: FTR I'm +1 on removing Retro tracker account, effective immediately (if any admin is around). -- ___ Python tracker <http://bugs.python.org/issue13868> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13868] Add hyphen doc fix
Sandro Tosi added the comment: On Mon, Jan 30, 2012 at 15:08, Boštjan Mejak wrote: > Can you fix all occurences of "floating point" (when in a role of > an adjective) to "floating-point" throughout Python docs? What I was asking is if *you* (since you care about the topic) would provide a patch fixing all that needs fixing. At that point there will be people interesting reviewing your patch, instead of people been told what to do. Regards, Sandro -- ___ Python tracker <http://bugs.python.org/issue13868> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13868] Add hyphen doc fix
Sandro Tosi added the comment: Wow.. do you really expect any positive outcome from you reply style? I'll pretend I didn't read your reply and let me rephrase my question like this: there are several occurrences of 'floating point' in python doc, are you going to fix all the ones that are wrong? -- ___ Python tracker <http://bugs.python.org/issue13868> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13868] Add hyphen doc fix
Sandro Tosi added the comment: There are a lot more occurrences of 'floating point' in our doc: are you going to fix them too? -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue13868> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13835] whatsnew/3.3 misspelling/mislink
Sandro Tosi added the comment: Thanks July, I've just committed your patches! -- nosy: +sandro.tosi resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue13835> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13605] document argparse's nargs=REMAINDER
Changes by Sandro Tosi : -- nosy: +sandro.tosi resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed versions: +Python 2.7, Python 3.2 ___ Python tracker <http://bugs.python.org/issue13605> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11551] test_dummy_thread.py test coverage improvement
Sandro Tosi added the comment: Hi Denver, do you have the time to address the review on rietveld and propose a new patch? -- ___ Python tracker <http://bugs.python.org/issue11551> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13478] No documentation for timeit.default_timer
Changes by Sandro Tosi : Added file: http://bugs.python.org/file24277/issue13478-py32.patch ___ Python tracker <http://bugs.python.org/issue13478> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13478] No documentation for timeit.default_timer
Sandro Tosi added the comment: I propose these 2 patches: I'm not exactly proud of - 'in a platform specific manner' in the first hunk - the second hunk I know that there should be a better way to express it, but since I can't get to it I'd just ask for suggestions :) -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file24276/issue13478-py27.patch ___ Python tracker <http://bugs.python.org/issue13478> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13826] Having a shlex example in the subprocess.Popen docs is confusing
Sandro Tosi added the comment: Maybe we can add a very small example before the whole note to show just how to use Popen in simple situation, and so the shlex part below will add more details for more advanced cases. -- nosy: +sandro.tosi versions: -Python 2.6, Python 3.1 ___ Python tracker <http://bugs.python.org/issue13826> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11948] Tutorial/Modules - small fix to better clarify the modules search path
Sandro Tosi added the comment: Thanks Terry for the ping, I've just committed it - thanks again to everyone for the help/suggestions. -- resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue11948> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13810] refer people to Doc/Makefile when not using 'make' to build main documentation
Sandro Tosi added the comment: The outdated command is addressed in issue#12415, and I think it's better to provide a precise command in devguide, so that if you don't use make you don't even need to understand where to grab the information to checkout third-party tools. Additionally, the whole way we're fetching those tools will be revisited soon. -- nosy: +sandro.tosi resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> Missing: How to checkout the Doc sources ___ Python tracker <http://bugs.python.org/issue13810> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12415] Missing: How to checkout the Doc sources
Sandro Tosi added the comment: that looks ok to me. -- ___ Python tracker <http://bugs.python.org/issue12415> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13801] The Python 3 Docs don't highlight nonlocal
Changes by Sandro Tosi : -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue13801> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12409] Moving "Documenting Python" to Devguide
Sandro Tosi added the comment: Éric, thanks for spotting it: removed. -- ___ Python tracker <http://bugs.python.org/issue12409> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12409] Moving "Documenting Python" to Devguide
Sandro Tosi added the comment: "Documenting Python" has been: - moved to devguide; http://hg.python.org/devguide/rev/5d4a90e568ed - removed from 2.7, 3.2 and default; http://hg.python.org/cpython/rev/8975f7d0fbf7 http://hg.python.org/cpython/rev/70c46599fb0e http://hg.python.org/cpython/rev/900c01e643a7 Thanks everyone! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue12409> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12409] Moving "Documenting Python" to Devguide
Sandro Tosi added the comment: On Sat, Jan 14, 2012 at 04:36, Éric Araujo wrote: > > Éric Araujo added the comment: > > I just replied to your python-dev email. I think you can update 2.7 to use > Sphinx 1.0 as soon as you’re down to a handful of warnings. thanks! I've just updated 2.7 to sphinx 1.0 - yay > When the migration is done, you can add the documenting doc to the devguide > and send a message to pydev to tell people to not commit changes to > Doc/documenting in CPython clones anymore. > > In the same email you can ask who to ask for setting up redirects (BTW, will > redirecting paths to fragments work? e.g. docs.py.o/documenting/style to > devguide/documenting#style-and-blah). When the redirects are up you’ll be > able to rm Doc/documenting. I just did that with: http://mail.python.org/pipermail/python-dev/2012-January/115520.html > Then we’ll open other reports to talk about the unrelated I mentioned and to > see how to stop downloading Sphinx from svn once per clone :) Ah yes, sure! Cheers, Sandro -- ___ Python tracker <http://bugs.python.org/issue12409> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13728] Description of -m and -c cli options wrong?
Sandro Tosi added the comment: Ah indeed, I could have looked at sys.path doc myself after all.. sorry for the noise. -- resolution: -> invalid stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue13728> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12409] Moving "Documenting Python" to Devguide
Sandro Tosi added the comment: Hi Éric, thanks for the review. On Fri, Jan 13, 2012 at 18:13, Éric Araujo wrote: > > Éric Araujo added the comment: > > About the devguide patch: > > a) The part about C roles and directives should probably mention version > specifics (:cmacro: for 2.7, :c:macro: for 3.x) — unless you make this bug > dependent on updating Sphinx to 1.0 for 2.7 and then all versions use > new-style :c:. yeah, I'd love to not write both rules/directives formats to later revert this addition, so ok, let's make this bug depending on the migration to sphinx 1.0 of the 2.7 version. I've sent a follow-up of that task to python-dev some days ago, and comments (and help!) would be welcome there too. > b) You probably want to use ref:documenting instead of :doc:documenting (we > always use ref) ah ok, I just used the same role that was there; updated to use :ref: - fixed that (just pushed on my repo, not updated patch yet) > Not related to your patch, but it made me think about them so I’m just > putting it out there for comments: Not sure we should keep the reST basics or > just redirect to docutils and Sphinx docs. as a matter of personal taste, I like small lists of commonly used commands/roles/directives/whatever in the doc, with additional links as needed, this give a quick idea (that's usually enough) on what to do but also the possibility for further digging (if one wants it). > Likewise, maybe it’s time to stop mentioning the old Latex-based docs. we can do that, but maybe at a later step? so now just put the doc in the canonical place, later let's refactor it, removing dead parts and so on? i'm fine anyhow > (A nit: there are a few instances of `markup` that should be :file:`etc` or > ``code``.) I'll fix them in the mean time. > About the cpython patch: You could just have said “rm Doc/documenting” :) eheh, well but a tiny tiny part remains :) if we go for a redirect to the devguide, I'm all for removing all that section from the doc; I left it there in case someone still refers directly to documenting/ or so (but indeed, all the sub-pages are no more reachable). > Georg, will you be the one to set up the docs.python.org redirects? I can provide the configuration, but I don't have access to the machine, so some admins must be there as well. Cheers, Sandro -- ___ Python tracker <http://bugs.python.org/issue12409> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12409] Moving "Documenting Python" to Devguide
Changes by Sandro Tosi : Added file: http://bugs.python.org/file24219/doc2devguide-cpython.patch ___ Python tracker <http://bugs.python.org/issue12409> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12409] Moving "Documenting Python" to Devguide
Sandro Tosi added the comment: Sure, sorry I didn't make it before; here attached the 2 patches, one against devguide, the other to default cpython repo. -- keywords: +patch Added file: http://bugs.python.org/file24218/doc2devguide-devguide.patch ___ Python tracker <http://bugs.python.org/issue12409> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13763] rm obsolete reference in devguide
Sandro Tosi added the comment: But we may explain what's behind: "after the mercury chemical element symbol" - what do you think? -- nosy: +sandro.tosi stage: -> patch review ___ Python tracker <http://bugs.python.org/issue13763> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13681] Aifc read compressed frames fix
Sandro Tosi added the comment: Hi Oleg, thanks for your interest in aifc module! I think that if the fix for audioop has a reason for itself to exists, then another issue (for that only) has to be filed and set the accordingly dependency on this one. -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue13681> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12409] Moving "Documenting Python" to Devguide
Sandro Tosi added the comment: Hi, i'm at last back with some work to show; I've integrated all the "Documenting python" doc into devguide, and the commits are in this sandbox: http://hg.python.org/sandbox/morph-devguide/shortlog/a92d431ef749 (`documenting` branch). I took the files from default branch and merged all of them in a single page. It might be a bit log, but it has the advantage (at least for me) that there you can find all the info you need for documenting python, a ctrl+f works and you don't need to follow tons of links to find what you're looking for. then I've removed all the info from default branch (here: http://hg.python.org/sandbox/morph/shortlog/e9a4276b19d4 in default-documenting branch) which left only documenting/index.rst as mainly a reference to the devguide. I don't know what would be the best way to handle this transition on the python doc side, maybe converting that to a simple Doc/documenting.rst as it's now index.rst? but what text to left? Comments are very welcome! -- stage: needs patch -> patch review ___ Python tracker <http://bugs.python.org/issue12409> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13762] missing section: how to contribute to devguide
Changes by Sandro Tosi : -- resolution: -> invalid ___ Python tracker <http://bugs.python.org/issue13762> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13762] missing section: how to contribute to devguide
Sandro Tosi added the comment: Hello Tshepang, The current section is at: http://docs.python.org/devguide/docquality.html#helping-with-the-developer-s-guide reachable from the mainpage looking for helping with documentation. it may be a little to condense but it is a good start (and it seems to cover the points you made in the issue): do you find it useful as it is? would you like to add something? -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue13762> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11205] Evaluation order of dictionary display is different from reference manual.
Changes by Sandro Tosi : -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue11205> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13743] xml.dom.minidom.Document class is not documented
New submission from Sandro Tosi : Hello, following up http://mail.python.org/pipermail/docs/2012-January/007026.html I noticed the whole Document class (and relative methods) is not documented. Maybe it is a choice to not document it, or maybe it's just a missing doc, dunno, the's why I'm opening this :) -- assignee: docs@python components: Documentation messages: 150935 nosy: docs@python, sandro.tosi priority: normal severity: normal stage: needs patch status: open title: xml.dom.minidom.Document class is not documented versions: Python 2.7, Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue13743> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13026] Dis module - documentation of MAKE_FUNCTION
Sandro Tosi added the comment: Hi Arnaud, would you like to provide a patch to update the MAKE_FUNCTION opcode description? That would speed up a bit the fix-up. Also, I don't have that clear what "For each keyword only default, ..." mean: are those the default values for keyword arguments? something else? Thanks in advance, Sandro -- nosy: +sandro.tosi stage: -> needs patch versions: +Python 3.2 ___ Python tracker <http://bugs.python.org/issue13026> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13122] Out of date links in the sidebar of the documentation index of versions 3.1 and 3.2
Sandro Tosi added the comment: Hi all, how can we fix it? or better, should we fix it? From a user POV, it is a weird to see 3.1 doc referring to 3.2 doc as "in development" then clicking on that link, being redirect to 3.3a0 doc and see there that 3.2 is stable (with no reference back to 3.1). Maybe we can adjust the sidebar in 3.1 references and do a manual rebuild or just wait for another security release? maybe we can discuss a policy for such things and write it in stone (aka devguide). -- nosy: +sandro.tosi ___ Python tracker <http://bugs.python.org/issue13122> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13729] Evaluation order for dics key/value
New submission from Sandro Tosi : Hello, following up http://mail.python.org/pipermail/docs/2011-December/006782.html , I'm opening this issue to have others confirmation of what's happening: echo -e "def ev(r):\nprint(r)\nreturn r\n\n{ev(1): ev(2), ev(3): ev(4)}" | ./python 2 1 4 3 (this applies for 2.7/3.2/default) so it seems the value expressions are evaluated before the key expressions, so the {expr1: expr2, expr3: expr4} in http://docs.python.org/reference/expressions.html#evaluation-order has to be updated in {expr2: expr1, expr4: expr3} Is that correct/can someone confirm this is the expected behavior? -- assignee: docs@python components: Documentation messages: 150804 nosy: docs@python, sandro.tosi priority: normal severity: normal stage: needs patch status: open title: Evaluation order for dics key/value versions: Python 2.7, Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue13729> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13728] Description of -m and -c cli options wrong?
New submission from Sandro Tosi : Hi, looking at http://mail.python.org/pipermail/docs/2011-December/006672.html I tried to replicate what the user said, and *it seems* that -c and -m doesn't add the current directory to the start of sys.path: $ echo -e "import sys\nprint (sys.path)" > dummy.py ; ./python -mdummy ['', '/usr/local/lib/python27.zip', '/home/morph/cpython/py27/Lib', '/home/morph/cpython/py27/Lib/plat-linux2', '/home/morph/cpython/py27/Lib/lib-tk', '/home/morph/cpython/py27/Lib/lib-old', '/home/morph/cpython/py27/build/lib.linux-x86_64-2.7-pydebug', '/usr/local/lib/python2.7/site-packages'] and $ ./python -c "import dummy" ['', '/usr/local/lib/python27.zip', '/home/morph/cpython/py27/Lib', '/home/morph/cpython/py27/Lib/plat-linux2', '/home/morph/cpython/py27/Lib/lib-tk', '/home/morph/cpython/py27/Lib/lib-old', '/home/morph/cpython/py27/build/lib.linux-x86_64-2.7-pydebug', '/usr/local/lib/python2.7/site-packages'] the same sys.path as from the interactive shell: $ ./python Python 2.7.2+ (2.7:f0666e56a552, Jan 7 2012, 16:31:06) [GCC 4.6.1] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import sys [38650 refs] >>> sys.path ['', '/usr/local/lib/python27.zip', '/home/morph/cpython/py27/Lib', '/home/morph/cpython/py27/Lib/plat-linux2', '/home/morph/cpython/py27/Lib/lib-tk', '/home/morph/cpython/py27/Lib/lib-old', '/home/morph/cpython/py27/build/lib.linux-x86_64-2.7-pydebug', '/usr/local/lib/python2.7/site-packages'] [38657 refs] So, is http://docs.python.org/using/cmdline.html#interface-options correct in saying "he current directory will be added to the start of sys.path (allowing modules in that directory to be imported as top level modules)."? (and so forth for -m option?) am I confused? -- assignee: docs@python components: Documentation messages: 150802 nosy: docs@python, sandro.tosi priority: normal severity: normal stage: needs patch status: open title: Description of -m and -c cli options wrong? versions: Python 2.7, Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue13728> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12415] Missing: How to checkout the Doc sources
Sandro Tosi added the comment: Hi Éric, did you reconsider the text of the patch or this issue just passed under your radar? -- ___ Python tracker <http://bugs.python.org/issue12415> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12042] What's New multiprocessing example error
Sandro Tosi added the comment: Thanks Davi for the report and Jordan for the patch! Jordan, a tip for your (hopefully) future contributions: for doc patches, please don't re-indent the whole paragraph, since it makes harder to identify the actual changes, just change what is needed, and the committer will take care (if needed) to re indent the paragraph. I've re-edited a bit and committed the fix in the active branches. -- nosy: +sandro.tosi resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: -Python 3.1 ___ Python tracker <http://bugs.python.org/issue12042> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11984] Wrong "See also" in symbol and token module docs
Sandro Tosi added the comment: Hi Davi, thanks for your report! I've removed the reference from symbol to parser, given this last module doesn't show anymore how to user symbol, and it's encouraging to use ast module instead. -- nosy: +sandro.tosi resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: -Python 3.1 ___ Python tracker <http://bugs.python.org/issue11984> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10772] Several actions for argparse arguments missing from docs
Sandro Tosi added the comment: Thanks Marc for the patch, I've just committed it. -- resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker <http://bugs.python.org/issue10772> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com