Hey Larry,
> http://hg.python.org/peps/rev/5019413bf672
> user:Larry Hastings
> date:Fri Jun 22 15:16:35 2012 -0700
> summary:
> Mark PEP 362 as accepted. Huzzah!
> diff --git a/pep-0362.txt b/pep-0362.txt
> --- a/pep-0362.txt
> +++ b/pep-0362.txt
> @@ -4,7 +4,7 @@
> Last-Mod
On 06/24/2012 07:21 PM, Nick Coghlan wrote:
Larry, I think this commit accidentally reverted a couple of entries
in Misc/NEWS.
It did; I restored them in the subsequent commit.
It's been a hectic couple of days,
//arry/
___
Python-Dev mailing list
On Mon, Jun 25, 2012 at 7:31 AM, larry.hastings
wrote:
> diff --git a/Misc/NEWS b/Misc/NEWS
> --- a/Misc/NEWS
> +++ b/Misc/NEWS
> @@ -59,9 +59,8 @@
> Library
> ---
>
> -- Support Mageia Linux in the platform module.
> -
> -- Issue #11678: Support Arch linux in the platform module.
> +- Issue
http://docs.python.org/devguide/buildbots.html contains a link to
http://python.org/dev/buildbot/, which redirects to
http://buildbot.python.org/index.html, which gives a 404.
I think it should point to http://buildbot.python.org/all/waterfall, or
maybe some subset of it.
Eric.
On 06/24/2012 08:32 PM, Nick Coghlan wrote:
> On Mon, Jun 25, 2012 at 6:14 AM, Eric V. Smith wrote:
>> On 6/24/2012 11:44 AM, Eric V. Smith wrote:
>>> On 6/24/2012 11:27 AM, Antoine Pitrou wrote:
> What's your timeframe for bug fixes today? I'd very much like to fix
> http://bugs.python.or
On Mon, Jun 25, 2012 at 6:14 AM, Eric V. Smith wrote:
> On 6/24/2012 11:44 AM, Eric V. Smith wrote:
>> On 6/24/2012 11:27 AM, Antoine Pitrou wrote:
What's your timeframe for bug fixes today? I'd very much like to fix
http://bugs.python.org/issue15039, but it will probably take me another
On 6/24/2012 11:44 AM, Eric V. Smith wrote:
> On 6/24/2012 11:27 AM, Antoine Pitrou wrote:
>>> What's your timeframe for bug fixes today? I'd very much like to fix
>>> http://bugs.python.org/issue15039, but it will probably take me another
>>> 2 hours or so.
>>
>> If it's a bugfix, it's not blocked
> Should we forget to care about performance, just because different
> setups might yield different results?
No, we are not forgetting about performance. You asked for a benchmark,
I presented one.
I fail to see your problem. I claim that the performance of namespace
packages is just fine, and pr
Hi all,
please consider the default branch frozen for new features as of now.
As you know, this also includes changes like large cleanups that cannot
be considered bug fixes. Contact me directly (IRC or mail) with urgent
questions regarding the release.
I hope that we will see the branch (and th
Le dimanche 24 juin 2012 à 15:51 -0400, PJ Eby a écrit :
>
> I don't really want to spread the idea that they're faster, either:
> the exact same benchmark can probably be made to turn out differently
> if you have, say, a hundred unzipped eggs on sys.path after the
> benchmark directory.
Yes, t
On Sun, Jun 24, 2012 at 3:27 PM, "Martin v. Löwis" wrote:
> >> In short, it's not worth worrying about, and definitely nothing that
> >> should cause people to spread an idea that __init__.py somehow speeds
> >> things up.
> >
> > The best way to avoid people spreading that idea would be to show h
>> In short, it's not worth worrying about, and definitely nothing that
>> should cause people to spread an idea that __init__.py somehow speeds
>> things up.
>
> The best way to avoid people spreading that idea would be to show hard
> measurements.
PJE wants people to spread an idea, not to avoi
Hello,
We only have a x86 Tiger OS X buildbot left. People wanting to see OS X
supported may decide to maintain a buildbot that will help us avoid
regressions.
See http://wiki.python.org/moin/BuildBot
Regards
Antoine.
___
Python-Dev mailing list
Py
On Sun, 24 Jun 2012 13:44:52 -0400
PJ Eby wrote:
> On Sun, Jun 24, 2012 at 3:51 AM, "Martin v. Löwis" wrote:
>
> > On 23.06.2012 17:58, Antoine Pitrou wrote:
> > > On Sat, 23 Jun 2012 17:55:24 +0200
> > > mar...@v.loewis.de wrote:
> > >>> That's true. I would have hoped for it to be recognized on
On Sun, Jun 24, 2012 at 3:51 AM, "Martin v. Löwis" wrote:
> On 23.06.2012 17:58, Antoine Pitrou wrote:
> > On Sat, 23 Jun 2012 17:55:24 +0200
> > mar...@v.loewis.de wrote:
> >>> That's true. I would have hoped for it to be recognized only when
> >>> there's at least one module or package inside, b
On 24 Jun 2012, at 14:29, Martin v. Löwis wrote:
> On 24.06.2012 14:52, Barry Scott wrote:
>> I see that issue 10910 needs a reviewer for a patch.
>>
>> I know the python code and C++ and offer to review
>> any patches to fix this issue.
>
> Is this even an issue for 3.x? ISTM that the C librar
>> Is this even an issue for 3.x? ISTM that the C library macros aren't
>> used, anyway, so I think this entire section could go from the header
>> files.
>
> $ grep isspace
> /Library/Frameworks/Python.framework/Versions/3.2/include/python3.2m/*.h
> /Library/Frameworks/Python.framework/Versions
On 6/24/2012 11:27 AM, Antoine Pitrou wrote:
>> What's your timeframe for bug fixes today? I'd very much like to fix
>> http://bugs.python.org/issue15039, but it will probably take me another
>> 2 hours or so.
>
> If it's a bugfix, it's not blocked by the feature freeze at all: you
> can commit af
On Sun, 24 Jun 2012 11:05:35 -0400
"Eric V. Smith" wrote:
> On 06/23/2012 06:54 AM, g.brandl-nos...@gmx.net wrote:
> > I've decided to make Tuesday 26th the big release day. That means:
> >
> > - Saturday: last feature-level changes that should be done before beta,
> > e.g. removal of packaging
On 06/23/2012 06:54 AM, g.brandl-nos...@gmx.net wrote:
> I've decided to make Tuesday 26th the big release day. That means:
>
> - Saturday: last feature-level changes that should be done before beta,
> e.g. removal of packaging
> - Sunday: final feature freeze, bug fixing
What's your timeframe
> --- a/PCbuild/pyproject.props
> +++ b/PCbuild/pyproject.props
> @@ -2,7 +2,7 @@
> xmlns="http://schemas.microsoft.com/developer/msbuild/2003";>
>
> python33$(PyDebugExt)
> - $(SolutionDir)python$(PyDebugExt).exe
> + $(OutDir)python$(PyDebugExt).exe
> $(OutDir)kill_python$(PyDeb
On 24.06.2012 14:52, Barry Scott wrote:
> I see that issue 10910 needs a reviewer for a patch.
>
> I know the python code and C++ and offer to review
> any patches to fix this issue.
Is this even an issue for 3.x? ISTM that the C library macros aren't
used, anyway, so I think this entire section
I see that issue 10910 needs a reviewer for a patch.
I know the python code and C++ and offer to review
any patches to fix this issue.
Having updated Xcode on my Mac I'm having to code
workarounds for this issue.
My understanding is that you cannot define
ispace, toupper etc as macros in C++ env
On Jun 24, 2012, at 12:08 AM, Martin v. Löwis wrote:
>Please propose something. I think the hexversion *is* user-friendly,
>since it allows easy comparisons (Py_LIMITED_API+0 >= 0x0303).
>Users that run into missing symbols will, after inspection of the
>header file, easily know what to do.
+
On Sun, Jun 24, 2012 at 5:08 PM, Nick Coghlan wrote:
> On Sun, Jun 24, 2012 at 5:00 PM, "Martin v. Löwis" wrote:
>>> This strikes me as in opposition to the Python-level policy of duck
>>> typing. Would it be more appropriate to, instead of asking if it's
>>> Python 3.3.0, ask if it's a Python th
On 23.06.2012 17:58, Antoine Pitrou wrote:
> On Sat, 23 Jun 2012 17:55:24 +0200
> mar...@v.loewis.de wrote:
>>> That's true. I would have hoped for it to be recognized only when
>>> there's at least one module or package inside, but it doesn't sound
>>> easy to check for (especially in the recursiv
On Sun, Jun 24, 2012 at 5:00 PM, "Martin v. Löwis" wrote:
>> This strikes me as in opposition to the Python-level policy of duck
>> typing. Would it be more appropriate to, instead of asking if it's
>> Python 3.3.0, ask if it's a Python that supports PY_FEATURE_FOOBAR? Or
>> would that result in a
> This strikes me as in opposition to the Python-level policy of duck
> typing. Would it be more appropriate to, instead of asking if it's
> Python 3.3.0, ask if it's a Python that supports PY_FEATURE_FOOBAR? Or
> would that result in an unnecessary proliferation of flag macros?
It would, hence I'
28 matches
Mail list logo
