Re: [Python-Dev] [RELEASE] Python 2.7.2 release candidate 1
Hi,
Le lundi 30 mai 2011 06:47:40, Ralf Schmitt a écrit :
> Benjamin Peterson writes:
> > The 2.7.2 changelog is at:
> > http://hg.python.org/cpython/file/439396b06416/Misc/NEWS
>
> The news file mentions that issue 1195 ("Problems on Linux with Ctrl-D
> and Ctrl-C during raw_input") is fixed. That's not true, see:
> http://bugs.python.org/msg135671
>
> Does one need special roundup rights to reopen issues?
Oh, I forgot that one. Please reopen the issue, I will apply your fix instead
of mine.
Victor
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [RELEASE] Python 2.7.2 release candidate 1
Victor Stinner writes: >> Does one need special roundup rights to reopen issues? > > Oh, I forgot that one. Please reopen the issue, I will apply your fix instead > of mine. I would love to do that, but as my above question implies I'm either too stupid to do that or I'm missing the rights to do it :) Cheers, - Ralf ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [RELEASE] Python 2.7.2 release candidate 1
Le lundi 30 mai 2011 10:46:39, Ralf Schmitt a écrit : > Victor Stinner writes: > >> Does one need special roundup rights to reopen issues? > > > > Oh, I forgot that one. Please reopen the issue, I will apply your fix > > instead of mine. > > I would love to do that, but as my above question implies I'm either too > stupid to do that or I'm missing the rights to do it :) Oops, I am stupid. I reopened the issue. Victor ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] pysetup as a top script
Hello If no one objects, I'll promote Tools/scripts/pysetup3 to a top level script that gets installed in scripts/ like 2to3, pydoc etc.. That way, people will be able to use it directly when installing, removing projects, or studying what's installed Cheers Tarek -- Tarek Ziadé | http://ziade.org ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Docs for the packaging module
Hi, The docs were not added alongside the code when packaging was merged back into CPython because they were not in a shape conforming with the rest of the docs. I’d like your input on layout so that I can fix this ASAP and merge the docs. (They would still require a lot of additions, fixes and improvements after that, but at least they’d be in the repo.) The easiest part is the library documentation, i.e. the docs for developers of packaging-related tools that want to use for example packaging.version or packaging.metadata to do their own stuff. These documents should go into Doc/library/packaging.*, I think this is a no-brainer. (Distutils has only a stub here, its API docs is mixed with its usage docs.) There is a guide for end-users, which contains an outdated copy of the old “Installing Python Modules” and a few documents about the new pysetup script (superseder of setup.py scripts), which are not integrated with the first document. I think those should supersede the existing distutils-based Doc/install tree. We want to advertise pysetup and packaging as the way of gettting modules in 3.3. A question remains: is it worthwhile to keep the old document somewhere? Last but not least, the doc for authors wanting to package and distribute their project (“Distributing Python Modules”, Doc/distutils). I think we should not overwrite this directory, because the directory name is tied to distutils and because there will be users needing that documentation (distutils is not removed). So, is it okay to create a new Doc/packaging directory and change the link on the docs front page from distutils to packaging? (Technical question: I think I’ll get a complaint from Sphinx that distutils is not included in any toctree; I’ll try adding a toctree from library/distutils to distutils/index and see if that works.) Thanks for reading ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython: removed spurious output
On 30.05.2011 17:54, Terry Reedy wrote:
>
>
> On 5/30/2011 6:25 AM, tarek.ziade wrote:
>
> Should not old_out be sys.stderr, since that is what you over-write and
> 'restore'?
>
>> +old_out = sys.stdout
>> +sys.stderr = StringIO()
>> +try:
>> +dist = self.run_setup('install_dist', '--prefix=' +
>> self.root_dir)
>> +finally:
>> +sys.sterr = old_out
And even more importantly, shouldn't this be "sys.stderr" instead of
"sys.sterr"?
Really, what happened to testing before you push?
Georg
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython: removed spurious output
On Mon, May 30, 2011 at 7:04 PM, Georg Brandl wrote:
> On 30.05.2011 17:54, Terry Reedy wrote:
>>
>>
>> On 5/30/2011 6:25 AM, tarek.ziade wrote:
>>
>> Should not old_out be sys.stderr, since that is what you over-write and
>> 'restore'?
>>
>>> + old_out = sys.stdout
>>> + sys.stderr = StringIO()
>>> + try:
>>> + dist = self.run_setup('install_dist', '--prefix=' +
>>> self.root_dir)
>>> + finally:
>>> + sys.sterr = old_out
>
> And even more importantly, shouldn't this be "sys.stderr" instead of
> "sys.sterr"?
Yes,
>
> Really, what happened to testing before you push?
I did test it, before and after my push, sir.
This was not to fix a test bug, but to avoid a spurious output in the tests.
> Georg
>
> ___
> Python-Dev mailing list
> [email protected]
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> http://mail.python.org/mailman/options/python-dev/ziade.tarek%40gmail.com
>
--
Tarek Ziadé | http://ziade.org
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] cpython: removed spurious output
On 30.05.2011 19:13, Tarek Ziadé wrote:
> On Mon, May 30, 2011 at 7:04 PM, Georg Brandl wrote:
>> On 30.05.2011 17:54, Terry Reedy wrote:
>>>
>>>
>>> On 5/30/2011 6:25 AM, tarek.ziade wrote:
>>>
>>> Should not old_out be sys.stderr, since that is what you over-write and
>>> 'restore'?
>>>
+old_out = sys.stdout
+sys.stderr = StringIO()
+try:
+dist = self.run_setup('install_dist', '--prefix=' +
self.root_dir)
+finally:
+sys.sterr = old_out
>>
>> And even more importantly, shouldn't this be "sys.stderr" instead of
>> "sys..sterr"?
>
> Yes,
>
>>
>> Really, what happened to testing before you push?
>
> I did test it, before and after my push, sir.
>
> This was not to fix a test bug, but to avoid a spurious output in the tests.
Well, I assumed changing sys.stderr would be noticed as changing the execution
environment.
But as I've now found out, the test class itself cleans up sys.stderr, so you
couldn't have noticed the bug. I apologize.
Georg
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] pysetup as a top script
On Tue, May 31, 2011 at 2:44 AM, Tarek Ziadé wrote: > Hello > > If no one objects, I'll promote Tools/scripts/pysetup3 to a top level > script that gets installed in scripts/ like 2to3, pydoc etc.. > > That way, people will be able to use it directly when installing, > removing projects, or studying what's installed Cool. Now I'm trying to remember if it was a list discussion or the language summit where you got the initial consensus on that approach... Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython: removed spurious output
On Mon, May 30, 2011 at 8:25 PM, tarek.ziade wrote:
> + old_out = sys.stdout
> + sys.stderr = StringIO()
> + try:
> + dist = self.run_setup('install_dist', '--prefix=' +
> self.root_dir)
> + finally:
> + sys.sterr = old_out
There's actually a helper for this in test.support:
with support.captured_stderr():
dist = self.run_setup('install_dist', '--prefix=' + self.root_dir)
Cheers,
Nick.
--
Nick Coghlan | [email protected] | Brisbane, Australia
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython: Close #12028: Make threading._get_ident() public, rename it to
On Tue, May 31, 2011 at 7:04 AM, victor.stinner wrote: > +.. function:: get_ident() > + > + Return the 'thread identifier' of the current thread. This is a nonzero > + integer. Its value has no direct meaning; it is intended as a magic > cookie > + to be used e.g. to index a dictionary of thread-specific data. Thread > + identifiers may be recycled when a thread exits and another thread is > + created. That's not quite true - the Thread id isn't relinquished until the Thread object itself is destroyed, rather than when the underlying thread finishes execution (i.e. the lifecycle of a_thread.ident is the same as that of id(a_thread)). Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] pysetup as a top script
On Tue, May 31, 2011 at 7:13 AM, Nick Coghlan wrote: > On Tue, May 31, 2011 at 2:44 AM, Tarek Ziadé wrote: >> Hello >> >> If no one objects, I'll promote Tools/scripts/pysetup3 to a top level >> script that gets installed in scripts/ like 2to3, pydoc etc.. >> >> That way, people will be able to use it directly when installing, >> removing projects, or studying what's installed > > Cool. > > Now I'm trying to remember if it was a list discussion or the language > summit where you got the initial consensus on that approach... The thread starts here: http://mail.python.org/pipermail/python-dev/2010-October/104535.html The pysetup top-level script was mentioned here: http://mail.python.org/pipermail/python-dev/2010-October/104581.html Cheers Tarek > > Cheers, > Nick. > > -- > Nick Coghlan | [email protected] | Brisbane, Australia > -- Tarek Ziadé | http://ziade.org ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
