of sync. It's hard enough to keep
stdlib code and stdlib docs in sync, but I think it will be even harder to
keep stdlib code in sync with devguide documentation. It will also be harder
to know what version of the devguide corresponds to what
t's an internal implementation detail. Then you can remove the entire
section from the stdlib docs and just document it in the code.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mai
want it versioned along side Python,
>but I still don't see why that would be a problem.
+1
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsu
27;m objecting to moving documentation for code to a different
repo than the code. If/when the stdlib is split out (which I support), then
the documentation should go with it.
Cheers,
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing li
y
used for third party applications. Mailman uses howtos for example.
BTW, Georg excellent work. I'm a big latex fan and long-time user,
but I do think that using reST will open the door to a lot more
contributions.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4
ed to build the documentation
properly installed. A pure-Python solution, even a lesser one, would
be a win if we can still produce top quality online and written
documentation from one source.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRlMC7XEjvBPtnXf
built-ins because any built-in could potentially be a value
in a mapping or a default argument. Have some super-secret module
global instantiated just for the purpose prevents that.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRlTf
gs can finally go in.
+1 for deprecating these. I don't have time to slog through the
stdlib and do the work, but I would be happy to help answer questions
about alternatives.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwU
gt; implementation of
> current python. Thanks.
There is also the new C/API sig:
http://mail.python.org/mailman/listinfo/capi-sig
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRo+XZHEjvBPtnXfVAQLjlwP/bv88BGiPr/A9jxFEHuiscCb1viEelnA9
R6zHiWHt4JkeR65P8Vtc20Ev+rigm
sier for the core to review and accept
contributions. diffs are so 20th century. :)
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRpeZYnEjvBPtnXfVAQL0ugQArei77bNsmv1hdrfs6RGinNiBdhNvSet8
vprjc3JgdV0iBltSX2KvHj+xOEd49ImDtKSws1uQNDLzIGMzv65/P03d3udwd2fy
Vr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 13, 2007, at 11:25 AM, Barry Warsaw wrote:
> I'll see if I can set up some public bzr mirrors of our svn
> repository for people to try it out. Or you could just use the bzr-
> svn plugin to get a local repository.
Silly me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 13, 2007, at 11:39 AM, [EMAIL PROTECTED] wrote:
> Barry> diffs are so 20th century. :)
>
> How do you compare two versions of something without some sort of
> diff?
Well okay, you caught me being flippant. :)
Sure, you v
ssary IIUC).
Having access is easy. Self-publishing might not be something people
want to do (it's certainly not something I want to do), but that's
not a requirement.
- -Barry
[1] <http://www.launchpad.net> which is a service provided by
Canonical. Full disclosure: I w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 13, 2007, at 12:24 PM, Facundo Batista wrote:
> 2007/7/13, Barry Warsaw <[EMAIL PROTECTED]>:
>
>> with merges. This means the end of posting patches because instead
>> what you would do is post the url to a branch
OnPureWindows
There's also a Tortoise-like extension available:
http://bazaar-vcs.org/TortoiseBzr
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRpfckHEjvBPtnXfVAQKArwP/aS20z5EcNT7GJSMepCORo34tE5SpF1g/
OMvRTervNDuUmjulgAHM9w9Chi3lOibM6eX0nJ8kHHzoaPrFDQkzh1/Gc+OZqfSA
quot;should" in PEP
9 would encourage but not enforce consistency, and I think that would
be fine.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRqXs7nEjvBPtnXfVAQLZWAP/UGGslCnGukFXJOvXoOyQE34baFAxKEyY
NmXmZnpGfnhNOgASG1zxpAzPd6PtHQUMzwk0FXwlHVHpwg9Lb+IxFGZ
d have been perfect, I think, if I could have opened the file
in text mode so that read() gave me strings, with universal newlines
and preservation of line endings (i.e. no translation to \n).
- -Barry
-BEGIN PGP SIGNATURE-
Version
an awesome sprint topic .
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRsPVQnEjvBPtnXfVAQIp9QP/Y9DCqvBdbDdVvTQp8gt4so2HW/AqRyZU
IF3SI/rrzMneslZRbU9PBlKbhq7oE/zwThpPss73W+64CoF2Z7N2dEGJJZncp+RK
bo1jyzG2bituz1ZqXRFW8t373XAWLrMusABXNAD5Ypfd1PfbmziFaa6ttyu2jl5O
4QWxPaw4qU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 1:30 AM, Paul Dubois wrote:
> The weekly summaries from the new bug tracker are disappearing
> somewhere
> between the tracker and python-dev. My attempt to post one by hand was
> rejected by python-dev-owner (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 10, 2007, at 1:43 AM, Anthony Baxter wrote:
> On Monday 10 September 2007, Paul Dubois wrote:
>> As a small boy I once knew wrote, I must not use bad words. (:->
>
> It's OK to use them about Barry, though, surely?
>
regrtest.
The standalone package has a testall script, but that should really
be converted to nosetests or some such.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRubgtXEjvBPtnXfVAQIGJgP/aeCOlybJj0sA3k6WOWMCOhugggLHHtO2
lu5v7hZZG5nqe5iApwxjbiyl
.org somewhere. Are there
> any HTTPS servers, or SSL-protected POP or IMAP servers, currently
> running on python.org already that I could use? The "use" is an SSL
> handshake with the server, once or twice per test run.
svn.python.org?
- -Barry
-BEGIN PGP SIGNATURE--
or arguments).
I wouldn't necessarily be opposed to new functions that did the line
splitting, but ideally, you could design an API that provided that
behavior for any of the existing alternatives in the base64 module,
without duplicating them all. It's not clear to me how you&#
ding a utility
> function, wrap_lines(), or some such to the module would suffice.
Does anything in textwrap already do the trick? If not, that might
be the best place to refactor similar code to.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRurm8HEjvBPtn
s to remember that for Py3k's email package. ;)
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRusNRnEjvBPtnXfVAQIpNgP/SosDYX/GDMolxcv3U2WrGzMjQa+gd8ai
J/Oaw2vdSf8H84eU9ziKaWHQtK0obS9XrnUTLUDyfAKObNffZVvldG1KUV9vAKhr
3JuNJ3xiIk7RKXdkKd5mA7SXXqRd80NVN26Za0H8b
be interested in, but it is, or can
be, mostly de-Mailmanized for use as a general library module. In
the particular use case it is designed for, it's been quite stable
for many years. Essentially it provides an NFS-safe lock file
implementation.
- -Barry
http://codebrowse.launc
e them in the stdlib, we could put them all
in a package and let the user decide which features they need.
I'm still planning on de-Mailman-ifying LockFile.py sometime soon.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRyFh4XEjvBPtnXfVAQIAgwQAk0Hf8df6zVGE0sMEfDGF
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 26, 2007, at 4:10 PM, [EMAIL PROTECTED] wrote:
>
> Barry> I don't think any one solution will work for everybody.
> I'm not
> Barry> even sure we can define a common API a la the DBAPI, but if
> B
of support, it could be implemented by this afternoon!
> (and backported to 2.4 within a week. ;-)
I know you're joking about the backporting. Neal, no sneaking this
into 2.5.2 now! :)
BTW, +1 on this. I like Fred's suggestion of property.set().
- -Barry
-BEGIN PGP SIGNATURE-
if I had approved of that technique I would have
> adopted one long ago.
It's also not as if you're writing some string value the second time,
so any typos in the name will be caught early on.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRyoLjnEjvB
orks
fine for me too.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBR02gvXEjvBPtnXfVAQJ4CQP+MuBSyL13DwLjFPon4l/lSXEBEa2XZ40U
LZMB/KF+VpgV8dNz/f1Bv7FA9pc/cIAU7qKKP8/vdAFQkkIPZhKzAgLlpBiOmK47
muNGYT5GsczfgM90/vzNqi2JQ8hWxpR/DIB+/59u2p/2zrADSdhVARt3tmJfivhI
9OY1e4VZk
ould be called __bruce__.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBR07aaXEjvBPtnXfVAQLlawQApbUkTl9BHm31evewnpn8OCqpz5RM4k6N
f4wfJ2HIZgDrFVkQLnBvWKp1t4b+HD+VGYHWxZgAjJ6+CFCFklkhOvxuDoyphuVu
bJLxUMrkra9PyM4Mrs6O8lc+z0YyqW/gGyEqtkXu/YVDK8bcEtVo6vQg9cjbtfSj
a7TLnkoBdUk=
s__
> alone and rename the __builtin__ module instead.
Hi Guido,
I saw it, and I like that change much better! There's no real need
to underscorify the module name.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBR1CaVnEjvBPtnXfVAQJk6Q
a bit heavier, that would be much better.
I tend to agree. The little bit of syntactic sugar doesn't really
seem worth it.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBR3xT9nEjvBPtnXfVAQIX/QQAmg9RczTAxHUe3qsry3F9DcUQZX32C9HS
VMETbSnoVS0Xrdm5J7cCYqjpHlPXLKRoF
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 7, 2008, at 9:01 AM, M.-A. Lemburg wrote:
> We could easily resolve that issue, if we add a per-user site-packages
> dir to sys.path in site.py (this is already done for Macs).
+1. I've advocated that for years.
- -Barry
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 7, 2008, at 10:12 AM, Guido van Rossum wrote:
> On Jan 7, 2008 6:32 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>> On Jan 7, 2008, at 9:01 AM, M.-A. Lemburg wrote:
>>> We could easily resolve that issue, i
moved.
>>
>> I think that's all that's needed. It would make playing with
>> easy_install/setuptools nicer to have this.
>
> Assuming that this is a true "site" directory (i.e., .pth files are
> recognized), then yes.
IMO, it should b
gt; resources as well, e.g. an optional sys.path lookup cache (pickled
> dictionary of known package/module file locations to reduces Python
> startup time).
Sure, why not?
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBR4KTn3EjvBPtnXfVAQLQlAP/R887WX0k3VNPoiyVs3qer
in use by various
> systems
> / people, so it would fit in better with existing practice.
I like the former path.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBR4VoJ3EjvBPtnXfVAQK9zQP/dup8RHQha0v9ZkYee+L5/8/fhvIHBEoP
MGkBxZUv79SmtnY4WWovS66NYAu
t;> was
>> pretty easy, because everything was unicode.
>
> Since this is a new feature, why bother with strings at all
> (even in 2.6) ?
>
> Use Unicode throughout and be done with it.
+1
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBR4
, unless you
> like
> my ideas and have specific questions, I will try to refrain from
> commenting further, lest I dig my own bike shed here :).
I feel pretty strongly that ~/bin should *not* be used. It makes
sense to me that ~/.local would mirror /usr/local.
- -Barry
-B
changes in. I
mean, a vendor is going to cherry pick the ones they want anyway, so
let's just make it easy for them to do this. That might mean
publishing the svn logs a long with the source release, or publishing
each diff and log message separately.
I would be bummed to rollback the
il
package from these branches, so that means that email 3.0.3 or 2.5.10
will have regressions.
Unless you're offering to also re-apply these changes after you make the
Python releases .
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http:/
to be clear it's a
different branch. 4.1.0 would be a fine number even if it's mostly
just a bookkeeping trick.
> Please let me know what you think.
What do you think of the above?
Thanks!
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUB
try to get to this today.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBR58c+nEjvBPtnXfVAQI1XgP/S9YUtkAC/x77alsmBYXtaoGZNrQ/QvtR
bziE1zzQ/Luexe9nt41JEaSbVyWb1dw0KZvpoDzqhqbLfhYAXCvJVFIlbw0U94bh
pf1G42L3U1YauzzUQL1Q9g0IT4jRMc3D3G8hwX4iOECEW8uHla9uAiqSl5r/V5af
K8BcRt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 29, 2008, at 1:01 AM, Martin v. Löwis wrote:
>> What do you think of the above?
>
> Sounds fine to me. I won't touch this then for the moment,
> please let me know when you are done rearranging things.
All done! Thanks.
s. It basically
tracks pdb prompts in a shell buffer so it makes it really easy to
just add a break point, run your code from the command line, and get
dual-window tracing from the shell.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBR6d4gHEjvB
eep maintaining python-mode.el and I
intend to update its syntax highlighting for Python 3 at some point.
But for the most part, it just works well enough for me.
The reason there are two Python modes is the same reason there is FSF
Emacs and XEmacs .
- -Barry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 4, 2008, at 5:34 PM, [EMAIL PROTECTED] wrote:
>
> Barry> The reason there are two Python modes is the same reason
> there is
>Barry> FSF Emacs and XEmacs .
>
> I remember something about some GNU perso
elopment?
>
>Brett> Usually the core has keywords, built-ins, etc. that have
> not been
>Brett> pushed to the release versions for various editors.
>
> Ah, okay. Barry mentioned something about adjusting the python-mode
> syntax
> tables to include Python 3.
you have to
do a bunch of manual crud to support these guidelines.
I recommend removing the guideline of 72 characters, and just say
everything, code, comments, and docstrings should be no wider than 79
characters.
- -Barry
-BEGIN PGP SIGNATURE-
Versio
lease the last Friday of
every month. For the alphas, it's basically what's in svn. This
gives us some time to experiment with the process out and see if we
like it enough to keep it going through the betas and final releases.
Comments?
- -Barry
-BEGIN PGP SIGNATURE
e case. I agree
>> with
>> Amaury.
>
> -1. There's just no way that 78 is enforceable. At Google, sticking to
> 80 is a continuous battle, and we use 2-space indents!
At my last job, I had a hard enough time getting people to stick with /
any/ limit! I ev
>> enough to
>> view it without wrapping.
>
> Yes, but svn/cvs diff is a particularly common use case. I agree with
> Amaury.
My main concern is that we have only one line length limit for
everything. If we want that to be 78 or 72 or whatever, okay (though
I still think 7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 21, 2008, at 12:30 PM, Guido van Rossum wrote:
> On Thu, Feb 21, 2008 at 9:15 AM, Barry Warsaw <[EMAIL PROTECTED]>
> wrote:
>> Why should docstrings and comments be limited to 72 characters when
>> code is limited
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 21, 2008, at 12:33 PM, Ron Adam wrote:
> Barry Warsaw wrote:
>
>> Why should docstrings and comments be limited to 72 characters when
>> code is limited to 79 characters? I ask because there is an ongoing
>> debate
e release going to make more sense than
> doing binary builds?
It very well might. See Christian Heimes's follow up re: Windows
builds. OTOH, I'm okay if at least for the alphas, the binary builds
lag behind the source releases, though I'd like to get the process as
streaml
nd few people not at PyCon will be available
>> during
>> the work week. OTOH, if we scheduled a bug day for the 29th, that's
>> two weeks after the conference, and we may have recovered from our
>> PyCon burnout at that point. What do people think?
>
> I'd r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 24, 2008, at 9:19 AM, Christian Heimes wrote:
> Barry Warsaw wrote:
>> I'd also like for us to consider doing regular monthly releases.
>> Several other FLOSS projects I'm involved with are doing this to very
>>
ce releases, though I'd like to get the
>> process as streamlined as possible.
>
> I can continue to provide Windows binaries if desired.
Great, thanks!
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR8MuDXEjvBPtnXfVAQJeJwP/R8MMAhOsyRtpxIIS
Windows machines so really
have no way of testing this either. Maybe one of the other Windows
gurus on this list can answer the question.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR8NFB3EjvBPtnXfVAQKZ1wP8Dv1aMdcbLM2NqpbWDdZLoeL7+91zVfTk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2008, at 7:11 PM, Christian Heimes wrote:
> Barry Warsaw wrote:
>> From the follow ups, it sounds like others can pitch in here. A
>> question though: is it reasonable to hold up the monthly release
>> because
&g
st_profile fail consistently for me on x86 Ubuntu Gutsy and Intel OS
X 10.5.2. It looks like the buildbots are failing here too -- does
anybody have time to fix these two tests?
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR8QaeXEj
On Feb 27, 2008, at 10:45 PM, Fred Drake wrote:
> On Feb 27, 2008, at 9:13 AM, A.M. Kuchling wrote:
>> Doing a code search finds a fair number of users of the module:
>> Zope's
>> BDBStorage, ...
>
> The BDBStorage is long gone at this point. Few are so unfortunate as
> to remember it (though a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 28, 2008, at 2:49 PM, Christian Heimes wrote:
> Hey Barry!
Hi Christian!
> When are you planing to freeze the code of the trunk and branches/py3k
> for the upcoming alpha releases? I'll merge the last modifications
> from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 28, 2008, at 3:03 PM, Chris Mellon wrote:
> On Thu, Feb 28, 2008 at 1:49 PM, Christian Heimes <[EMAIL PROTECTED]>
> wrote:
>> Hey Barry!
>>
>> When are you planing to freeze the code of the trunk and branches
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 28, 2008, at 4:03 PM, Eric Smith wrote:
> Barry Warsaw wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>> On Feb 28, 2008, at 2:49 PM, Christian Heimes wrote:
>>> Hey Barry!
>> Hi Christian!
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 28, 2008, at 5:07 PM, Stephen J. Turnbull wrote:
> Barry Warsaw writes:
>
>> I plan on cutting the alphas for 2.6 and 3.0 at about 6pm Eastern
>> (UTC-5) time or 2300 UTC. Let's freeze the tree one hour prior to
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 29, 2008, at 5:21 AM, Georg Brandl wrote:
> Scott Dial schrieb:
>> Barry Warsaw wrote:
>>>> Alterntaively, I guess you could just suggest that people check the
>>>> buildbot page for their platforms before d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 29, 2008, at 7:39 AM, Nick Coghlan wrote:
> Barry Warsaw wrote:
>> Think of it this way: the alphas are for /us/ as much as for our
>> users.
>
> In that vein, I think the monthly alphas may also help as a means
&
that's not something I think we're ready for. The bigger
question though is whether we as a development community would change
the way we work so that nothing lands if it doesn't pass all the
tests. We'd be trading some inconvenience (and administrative
headaches) for b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 29, 2008, at 1:08 PM, Eric Smith wrote:
> Barry Warsaw wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>> On Feb 28, 2008, at 4:03 PM, Eric Smith wrote:
>>> Barry Warsaw wrote:
>>>> -BEG
ciated. I
will cut 3.0a3 tomorrow (Saturday) as early as possible.
time-to-start-drinking-ly y'rs,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR8jdyXEjvBPtnXfVAQJSowQAgIqqYKYPvzEMtvtAHiNC+OkMpO3vxelh
9kcAgXClhCS47wAMc9viJsb5Uo12f7TlOURkEjuMZ13jrBri+HCFtrAG
s do you take
when you need to expose a new major release on the website?
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR8lkF3EjvBPtnXfVAQLjtQP/cyIu6i/3hL7RMyJjwi5UWaVelq+6+DjX
c8P6aLT0Gq2jIIacwt2P5lWYGx5D2nahoLCkLoA4M3avHM6UiT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 10:38 AM, Steve Holden wrote:
> Barry Warsaw wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On Mar 1, 2008, at 12:36 AM, Steve Holden wrote:
>>
>>> If you can document the
ll to be determined.
Enjoy,
- -Barry
Barry Warsaw
[EMAIL PROTECTED]
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR8mlu3EjvBPtnXfVAQKePAQAgx6w9wztfJaSWkbKrbwur2U6t6o5aIY5
pyMa00CZWY06p8099BztcSjgp5
d stale too. If you know anything
about distutils version numbers and the process for updating them,
please contact me.
There's no Misc/RPM/python-3.0.spec file so I skipped that step too.
Sean, do you know anything about that?
That's it. See you again next time :). Let me know if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 1:56 PM, Christian Heimes wrote:
> Barry Warsaw wrote:
>> In this case, there was a lot more work to do because 2.6 wasn't tied
>> in at all. Add to the fact that I didn't have any experience
w/ is. Only a
> couple of people - mostly Georg and Andrew - are updating the files.
I think it's okay if these lag behind during the alphas, but it would
be good to start whipping these in shape by the time we start
releasing betas.
Thanks,
- -Barry
--
.l.p. announcement.
>
> I just fixed that. The files were there; just the links were wrong.
Thanks for fixing these Martin!
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR8nY1HEjvBPtnXfVAQJ3YgP/TYr0X5vRqvVDEMgsHxHuiSuYZCIr8y36
ibAh3RAGeLLK7C7NiOyAfxkesf91
101.
Anyway, that's the kind of tool I plan on building (or perhaps with
help from others -- hi Benjamin) for the next alpha round.
Cheers,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR8ngyHEjvBPtnXfVAQKYaAP+JzIj8HiwVYIJLMyxh+Glq57YQozOh2bB
XI
I definitely won't change
> it to work out of the box. If 2.4.4 compiled out of the box on this
> box,
> it would have been a regression and would have to be fixed. IIUC,
> 2.4.4
> won't compile on 10.5, either, and Python 2.4.5 will have no code to
> port it to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 2, 2008, at 1:21 AM, Stefan Behnel wrote:
> Barry Warsaw wrote:
>> On behalf of the Python development team and the Python community,
>> I'm
>> happy to announce the first alpha release of Python 2.6, and the
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 28, 2008, at 4:56 PM, Fred Drake wrote:
> On Jan 28, 2008, at 4:47 PM, Barry Warsaw wrote:
>> The problem is that I make separate releases of the standalone email
>> package from these branches, so that means that email 3.0.3 or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 7:28 PM, [EMAIL PROTECTED] wrote:
>
> Barry> The dependency on gtk is unnecessary and means it can
> effectively
>Barry> only be run on Linux. Specifically it means I can't do
> releases
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 10:29 PM, Stephen J. Turnbull wrote:
> The fact that Barry found Anthony's process unusable is IMO not a
> reflection on either Barry or Anthony's code. Release processes seem
> to be highly personal, even with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 2, 2008, at 1:54 AM, Georg Brandl wrote:
> Barry Warsaw schrieb:
>
>> PEP 101 is sorely out of date, especially with regards to updating
>> web
>> content and the Python documentation. I think I now know how to
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 9:00 PM, Alex Martelli wrote:
> On Sat, Mar 1, 2008 at 11:11 AM, Barry Warsaw <[EMAIL PROTECTED]>
> wrote:
> ...
>>> I also propose translations of the shorter text to important
>>> languages
you want the next monthly alphas to be? :)
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR91OWHEjvBPtnXfVAQIL/gP/T5TqGLt6Z7LD3/vEKt/0qjZErkOQmmFH
BciuGOs6CCud//N4fsSev2CBmeAQ/RspHhjLSSKBd6H4rimZWv5ePo0gMC2N7nGY
1wpUvixaZpYol4zywjBQRO+bjlnZtdt4WG09DdMrn0MsYHNpVFaAPTWx4X
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 16, 2008, at 8:51 AM, Guido van Rossum wrote:
> Python 3.0 and 2.6 are coming along really nice. I am optimistic that
> we can make the projected August date for the final releases of 2.6
> and 3.0. As you may remember, Barry (the ne
that we should plan to release a first
> beta in June and a second one in July. That means we have time for
> only two more alpha releases (April and May). I'm thinking of 1-2
> release candidates 1-2 weeks ahead of the final release. Barry can
> make up a more detailed timetab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 16, 2008, at 3:56 PM, Guido van Rossum wrote:
> On Sun, Mar 16, 2008 at 12:24 PM, Barry Warsaw <[EMAIL PROTECTED]>
> wrote:
>> I mentioned this to Guido and got a positive response, so let me
>> state
>> my pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 16, 2008, at 6:46 PM, Barry Warsaw wrote:
>
> 'critical' is fine (or 'immediate'). My problem before was that I
> couldn't do one query that gave me all the critical issues for both
> 2.6 and 3.0. That ce
these issues up higher if we want to fix them
before the next alpha of course.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR97KeXEjvBPtnXfVAQKcCAP/YxZ7LQJepi9pg5IONjg1NePJSWwqggG7
rdFexmeHVockllBr5GMMmYgnr+jytnNDtRMTdy/uBvn3Ocl8+JRUHb5g/sDz2KQr
usHcHnqIgkoQIgBnH
s red. Embarrassing
Pycon pictures of you will be posted if such broken revisions cause us
to slip a release, and remember, we know how to use GIMP.
On behalf of everyone, here's to an awesome release!
-Barry
Python 2.6/3.0 release manager
PEP: 361
Title: Python 2.6 and 3.0 Release Schedule
Version:
h and ignored, or
it gets moved to release blocker and gets fixed.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR99JvnEjvBPtnXfVAQJwuwQAh5mhXdwg7t9FAsNXJ69OoPM6qj37OjP4
+3SjZMn9A1qObFB7biUV6P47KwydzDskMaswifMv9eV94+ccb0mIlDC/SgdjB9h8
JtuJq6mZ1nIUqQSLtX4W6op4G/
.g. stuff checked in that doesn't even build).
I think neither of these use cases should get that far. Neal and I
talked it over and we're in agreement that if a commit makes the
buildbots go red or breaks the build, we're going to just revert it.
Tough luck Joe Dev, p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 18, 2008, at 2:04 AM, Travis Oliphant wrote:
>
> Hey Barry,
>
> Thanks for putting this PEP together. This is really helpful.
Hi Travis... thanks!
> I didn't see discussion of PEP 3118 and it's features back-port
'm in the camp that Gabriel describes. I prefer assertEqual/
assertRaises and failIf/failUnless.
I like the latter because it reads nicely: fail unless [this thing is
true], fail if [this thing is true].
OTOH, I'd rather there be OOWTDI so whatever the consensus is is fine
with me.
privileges can commit to it and help further develop setuptools.
If not, why not and what is the sandbox setuptools used for?
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iQCVAwUBR+Eca3EjvBPtnXfVAQLabwP9F8NtQX6YsDXJMHiByCGILPAQ2NgtaIzg
en6yYbhl5IAweTr0DtWzxRXjSGMifK/D
1801 - 1900 of 2826 matches
Mail list logo
