Sandro Tosi added the comment:
> R. David Murray added the comment:
>
> Note that based on my experience with the conversion of compileall to
> argparse,it is important to have good tests. Of course, regrtest itself has
> no tests...
Indeed that's quite funny :) anyhow
Changes by Sandro Tosi :
--
nosy: +sandro.tosi
___
Python tracker
<http://bugs.python.org/issue10967>
___
___
Python-bugs-list mailing list
Unsubscribe:
Sandro Tosi added the comment:
I finally had the time to look more closely to the issue, and I'd like to hear
some comments on the info visualization.
Currently we have --help option to print:
Now, AFAIK argparse it's not so flexible, so we have to draw a line and
Sandro Tosi added the comment:
> R. David Murray added the comment:
>
> What about putting the addition option details in the epilog?
maybe it loose the fact that all the doc/explanation for regrtest
options were available from the command-line?
what about a --more-help op
Sandro Tosi added the comment:
On Tue, Jan 25, 2011 at 02:20, R. David Murray wrote:
> That might be handy. I thought you were trying to roughly reproduce the
> current help (which dumps it all out at once), which is why I suggested
> epilog.
actually that was my objective :) b
Sandro Tosi added the comment:
On Tue, Jan 25, 2011 at 19:29, R. David Murray wrote:
>
> R. David Murray added the comment:
>
> Hmm. Am I misunderstanding something about epilog, then? I thought it was
> placed at the end of the other help text?
Sorry I get confused by the
Sandro Tosi added the comment:
Sure, that would be really interesting to do, and I do commit to write
a "test suite to the tool that runs the python test suite" :)
What I'm asking is: how would you do that? I'm quite new as
contributor so the ideas of experienced core devs
Sandro Tosi added the comment:
As suggested by David, I made it possible to specify an alternative test
directory by introducing '--testdir DIR' cli option: attached the patch,
comments are welcome :)
What about STDTESTS/NOTTESTS in case --testdir is specified? Currently they are
Sandro Tosi added the comment:
shouldn't we use the same method also for --coverdir (that currently faild the
"least surprise" test when specifying a relative path) replacing
coverdir = os.path.join(os.getcwd(), a)
with
coverdir = os.path.join(supp
New submission from Sandro Tosi :
Hi, following up msg127157 here's a patch to allow for relative path when using
--coverdir.
The current solution uses getcwd() but since CWD is replaced by a temporary
location before calling main(), then the resulting dir is in an unexpected
loc
New submission from Sandro Tosi :
from msg127153 + msg127157 + msg127172 I prepared this patch to introduce a new
cli option to regrtest.py, --testdir DIR, that allows to specify a different
location for the directory containing the test files.
along the way, I added a description of what
Changes by Sandro Tosi :
Removed file: http://bugs.python.org/file20541/issue10848-testdir-py3k.patch
___
Python tracker
<http://bugs.python.org/issue10848>
___
___
Pytho
Sandro Tosi added the comment:
I've created two new issues (David, I think I've lost why I'd need 3 :) )
* issue11030 - finally allows to specify a relative dir with --coverdir
* issue11031 - to expose --testdir in order to specify a different location of
the directory c
New submission from Sandro Tosi :
Hi,
following up with issue10848, here's another preparatory step:
- renamed test_future[12].py to future_test[12].py, to clearly identify the as
not unittest files (and so facilitate the autodiscovery introduction)
- adapted test_future.py for the fil
Changes by Sandro Tosi :
--
title: test_future - rename not-unittest files to redure regrtest.NOTTESTS an
empty set -> test_future - rename not-unittest files to make regrtest.NOTTESTS
an empty set
___
Python tracker
<http://bugs.pyth
Sandro Tosi added the comment:
I was looking at this bug and tried to reproduce it, but I can't :( I extracted
this code:
part1 = 'Content-Type: multipart/related;
start=;
boundary=--1JBOHhxKNnWgkmE17ZJ2Cy\r\nContent-Location:
http://localhost/page1.html\r\nSubject: =?ut
Changes by Sandro Tosi :
--
nosy: +sandro.tosi
___
Python tracker
<http://bugs.python.org/issue6818>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Sandro Tosi :
--
keywords: -patch
___
Python tracker
<http://bugs.python.org/issue6818>
___
___
Python-bugs-list mailing list
Unsubscribe:
Sandro Tosi added the comment:
Lucky as I can be, I have 2.5.5 here and I can confirm that with this version
the code above fails - so I think this issue can be closed as fixed by
issue5610 (I hope I correctly set all the fields, if not please let me know :)).
--
resolution
Sandro Tosi added the comment:
Jan, are you still interested in this?
--
___
Python tracker
<http://bugs.python.org/issue6253>
___
___
Python-bugs-list mailin
Sandro Tosi added the comment:
Hello Felix/Don,
are you still interested in seeing this fixed in smtplib? If so, what about
incorporating Martin's suggestions and propose a new patch for review?
--
nosy: +sandro.tosi -Felix Schwarz
stage: -> tes
Sandro Tosi added the comment:
On Tue, Feb 8, 2011 at 23:40, Éric Araujo wrote:
>
> Éric Araujo added the comment:
>
> Do you have any pointer about those .nfs* files? Are there other (build)
> tools that ignore them? Is it always safe to skip .nfs* files, or only
> .
Sandro Tosi added the comment:
Hi all,
I was looking at this issue and thought: ok the module documentation uses
send() not correctly, so we should fix that; the fastest solution is using
sendall().
But then searching fro some examples in the code on internet, I found that the
python docs
Sandro Tosi added the comment:
How should we move forward with this issue?
J Evens: are you willing to split the patch in smaller ones that can be more
easily managed/reviewed/applied?
Antoine: do you think it's worth the effort?
I can also try to split the patch, but what branch sho
Sandro Tosi added the comment:
Hi David, AFAIUI in py3k branch I see email module has version 5.1.0 so I guess
the new email module will be targetting 3.3 - am I correct? what should we do
with this issue?
--
nosy: +sandro.tosi
stage: -> patch rev
Sandro Tosi added the comment:
Hi Georg, are you planning to backport this patch also to 3.1 or else can we
close this issue? Cheers!
--
nosy: +sandro.tosi
stage: -> committed/rejected
___
Python tracker
<http://bugs.python.org/iss
Sandro Tosi added the comment:
Sean, could you please explain a bit more what are your concerns about this
patch?
Anyhow, the code has slightly changed and currently John is not maintaining
offlineimap anymore, but what seems the most recent version can be found at:
https://github.com
Changes by Sandro Tosi :
--
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue6626>
___
___
Python-bugs-list mailing list
Unsubscri
Sandro Tosi added the comment:
Hi Mark, would you like to write some tests about the proposed change? Antoine
gave a fast look at the issue and believe it's acceptable for 2.7.
--
nosy: +sandro.tosi
stage: -> test needed
versions: +Python 2.7 -Py
Sandro Tosi added the comment:
Hi, optparse is now deprecated, and argparse is the replacement, so I'm closing
this report.
--
nosy: +sandro.tosi
resolution: -> wont fix
stage: needs patch -> committed/rejected
status: open -> closed
Sandro Tosi added the comment:
Hi Daniel, did you read Steven suggestions? are you willing to propose a patch
about your feature request against argparse (optparse is deprecated and no more
under development in stdlib)?
--
nosy: +sandro.tosi
Sandro Tosi added the comment:
Hi, since optparse is now deprecated (in favor of argparse) and in a year and
half there was not progress on this, I'm closing this report.
--
nosy: +sandro.tosi
resolution: -> wont fix
stage: -> committed/rejected
status: ope
Sandro Tosi added the comment:
Hi Steven, I'm not exactly getting what you're meaning here: are you actually
saying to replace every occurrence of 'option' with 'argument' in the whole
argparse module doc, or just make it stronger in the mentioned line that what
Sandro Tosi added the comment:
I've prepared a simple patch: what do you think about it?
--
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org
Sandro Tosi added the comment:
now even with patch attached :)
--
keywords: +patch
Added file: http://bugs.python.org/file20747/issue10423.patch
___
Python tracker
<http://bugs.python.org/issue10
New submission from Sandro Tosi :
Hi, following up
http://mail.python.org/pipermail/docs/2011-February/003096.html I wrote a patch
to introduce the 'Host' header in the HTTP example of asyncore doc. I've also
fixed an indentation error with the last 2 lines of the same examp
New submission from Sandro Tosi :
Hi, following up
http://mail.python.org/pipermail/docs/2011-February/003095.html I'm attaching a
simple patch to avoid a traceback similar to this when a client disconnects:
error: uncaptured python exception, closing channel <__main__.EchoHandler
1
Changes by Sandro Tosi :
--
components: +Documentation
___
Python tracker
<http://bugs.python.org/issue11232>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Sandro Tosi :
Hi, following up
http://mail.python.org/pipermail/docs/2011-February/003083.html we have a chat
on #python-dev on the topic, the situation is
- all started with os.lchmod() and as.lchflags() methods not available on a
Debian system
- that's because
Sandro Tosi added the comment:
On Thu, Feb 17, 2011 at 20:22, Carl Chenet wrote:
>>>> sysconfig.get_config_var('SO')
> '.cpython-32m.so'
>
> A dot at the beginning of the string could be missing in the example of the
> current documentation. Thi
New submission from Sandro Tosi :
Hi, following up
http://mail.python.org/pipermail/docs/2011-February/003088.html, here's a patch
to make sets.html big red notice :) refer to set/frozenset into stdtypes page
with a couple of links.
--
assignee: sandro.tosi
components: Document
Sandro Tosi added the comment:
well, since we are at it, sed 's/abasic/a basic/' in the first line of echo
server example; I'm too lazy to regenerate the patch tho :)
--
___
Python tracker
<http://bugs.pyt
New submission from Sandro Tosi :
hi, following up
http://mail.python.org/pipermail/docs/2011-February/003099.html, here's a patch
to add '}' to metachars, currently missing.
--
assignee: sandro.tosi
components: Documentation
files: regex-howto-add-missin-metachar-py3k
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
> specif
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 track
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
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.
Sandro Tosi added the comment:
Éric, thanks for spotting it: removed.
--
___
Python tracker
<http://bugs.python.org/issue12409>
___
___
Python-bugs-list mailin
Changes by Sandro Tosi :
--
nosy: +sandro.tosi
___
Python tracker
<http://bugs.python.org/issue13801>
___
___
Python-bugs-list mailing list
Unsubscribe:
Sandro Tosi added the comment:
that looks ok to me.
--
___
Python tracker
<http://bugs.python.org/issue12415>
___
___
Python-bugs-list mailing list
Unsubscribe:
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.
Ad
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
___
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
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 suggestion
Changes by Sandro Tosi :
Added file: http://bugs.python.org/file24277/issue13478-py32.patch
___
Python tracker
<http://bugs.python.org/issue13478>
___
___
Python-bug
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/issue11
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.or
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.pyth
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.o
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 a
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
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 ad
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: ope
Changes by Sandro Tosi :
--
components: -None
versions: -Python 2.7
___
Python tracker
<http://bugs.python.org/issue13939>
___
___
Python-bugs-list mailin
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 ve
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
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 hu
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.
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.or
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 n
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 m
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 refrain
Changes by Sandro Tosi :
--
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
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 too
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/is
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/issue14
Sandro Tosi added the comment:
see msg155067
--
nosy: +sandro.tosi
versions: -Python 2.6, Python 3.1
___
Python tracker
<http://bugs.python.org/issue14
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
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.or
Changes by Sandro Tosi :
--
nosy: +sandro.tosi
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
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/i
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 differen
Changes by Sandro Tosi :
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
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.or
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.or
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/is
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.or
Changes by Sandro Tosi :
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
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.or
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.pyth
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.or
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: ->
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 an
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
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/is
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/issue14
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
resol
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.pyt
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
Changes by Sandro Tosi :
--
nosy: +sandro.tosi
___
Python tracker
<http://bugs.python.org/issue12947>
___
___
Python-bugs-list mailing list
Unsubscribe:
301 - 400 of 426 matches
Mail list logo
