On Mar 26, 2012, at 12:22 AM, Terry Reedy wrote:
> Does the css specify Courier New or is this an unfortunate fallback that
> might be improved? Perhaps things look better on max/*nix?
I just checked pydoctheme.css and Courier New is not specified there.
It only specifies monospace.
That's a d
On Sep 1, 2011, at 9:30 PM, Steven D'Aprano wrote:
> Antoine Pitrou wrote:
>> Le jeudi 01 septembre 2011 à 08:45 -0700, Guido van Rossum a écrit :
>>> This is definitely thought of as a separate
>>> mark added to the e; ë is not a new letter. I have a feeling it's the same
>>> way for the French
On May 4, 2010, at 8:41 AM, Antoine Pitrou wrote:
> I think we should reindent all 3 branches. Most of the work can probably be
> scripted (str.replace("\t", " " * 4)), and then a visual pass is necessary to
> fix vertical alignments and the like.
>
> I think we should reindent all 3 branches.
On Apr 14, 2010, at 4:40 PM, Martin v. Löwis wrote:
>> I think you just need to supply to configure
>>
>> MACOSX_DEPLOYMENT_TARGET=10.4
>>
>> and have the appropriate SDK installed with Xcode.
>
> Wouldn't that break 10.3 compatibility (seel below)?
I was replying to your point about 10.4 bui
On Apr 14, 2010, at 3:37 PM, Martin v. Löwis wrote:
> I'm not sure whether 10.5 would be sufficient - it may be that you need to go
> back to 10.4 (*).
I think you just need to supply to configure
MACOSX_DEPLOYMENT_TARGET=10.4
and have the appropriate SDK installed with Xcode.
I belie
On Apr 14, 2010, at 3:30 PM, Simon Brunning wrote:
> On 14 April 2010 20:02, wrote:
>> I ran a Mac OSX buildbot for the community buildbots for awhile but never
>> did figure out at the time how to get it to fire up on reboot. That was a
>> few years ago. I think today that would easily be a
On Mar 19, 2010, at 1:15 PM, Terry Reedy wrote:
> On 3/19/2010 10:22 AM, R. David Murray wrote:
>
>> This can be done by anyone just by saying, eg: 'see issue 1234' (roundup
>> turns that into a link),
>
> That should be 'see issue #1234' to get the autolink.
> From http://wiki.python.org/moin/
On Feb 4, 2010, at 4:59 AM, Barry Warsaw wrote:
> I still think this should go in 2.6.5. The patch does not apply to the
> current 2.6 branch because of changes in setup.py. If the patch is ported,
> reviewed and works with no regressions (when libreadline is both installed on
> OS X 10.5 and
On Feb 3, 2010, at 3:07 PM, Martin v. Löwis wrote:
>> This patch is still waiting a review and backporting from trunk.
>>
>> http://mail.python.org/pipermail/python-dev/2009-October/092771.html
>>
>> Can we get it in?
>
> Only if one of the Mac people checks it in.
It's already checked in the
On Feb 2, 2010, at 1:08 PM, Barry Warsaw wrote:
> I'm thinking about doing a Python 2.6.5 release soon. I've added the
> following dates to the Python release schedule Google calendar:
>
> 2009-03-01 Python 2.6.5 rc 1
> 2009-03-15 Python 2.6.5 final
>
> This allows us to spend some time on 2.6.
On Oct 13, 2009, at 8:23 AM, Barry Warsaw wrote:
On Oct 8, 2009, at 8:45 AM, Zvezdan Petkovic wrote:
On Oct 7, 2009, at 2:09 PM, Barry Warsaw wrote:
I want us to be very careful about 2.6.4. This isn't a normal bug
fix release, it's specifically there to remove the brown pape
On Oct 7, 2009, at 2:09 PM, Barry Warsaw wrote:
I want us to be very careful about 2.6.4. This isn't a normal bug
fix release, it's specifically there to remove the brown paper bag
of 2.6.3 from our heads. So let's be conservative and fix this one
in 2.6.5.
Can we get the readline patch
On Sep 9, 2009, at 2:19 PM, Ronald Oussoren wrote:
MacOS X 10.6 support should be stable now, except for a critical issue
with IDLE: opening a new window hangs IDLE (issue 6864).
That said, I haven't scanned the issue tracker for more 10.6 related
issues.
I just opened issue 6877 and provid
On Mar 25, 2009, at 11:02 PM, Nick Coghlan wrote:
That is, the full workflow that should really be happening is
something like the following:
Developer(s)
|
V
(distutils/setuptools/pip/zc.buildout/etc)
On Mar 13, 2009, at 2:31 PM, Martin v. Löwis wrote:
Think about the security implications of a file name that is in
advance known to an attacker as well as the fact that the said file
will replace an *important* system file.
You should always use O_EXCL in that case. Relying on random name
On Mar 12, 2009, at 3:15 PM, Martin v. Löwis wrote:
You still wouldn't use the tempfile module in that case. Instead, you
would create a regular file, with the name base on the name of the
important file.
If the file is *really* important, you actually want to use a
temporary, randomly chose
On Feb 27, 2009, at 3:31 PM, Brett Cannon wrote:
We should probably put these, and the Mercurial information on the
python.org website, perhaps as siblings of the Bazaar information.
Or maybe it should all move to the wiki.
Until we are willing to say these mirrors are not experimental all
17 matches
Mail list logo
