While I have not been involved in the release process for like 15 years or
more, I would like to point out that breaking changes mean the distros are
less likely to ship them, and be less likely to trust updates.
Trying to get RH &c to stop shipping 1.5.2 was a huge effort.
Always, any time when
.
You don’t need to worry about indentation, and you can indent whenever
you want.
I hope that you consider these issues and fix them in Python 4 (if you ever
make it).
Sincerely, Anthony, age 10.
--
mmm#
## m mm mm#mm # mmmmm m mm m m
earch(pattern, line)
if match is not None:
name = match.group(1)
if name and validate(name):
return name
else:
# No valid case
else:
# No Match case
Best,
Matěj
--
--
Anthony Flury
email : *anthony.fl...@btinternet.com*
Twitter : *@Tony
on the speed of that operation; without
consideration of how often that operation is used.
On 17/05/18 09:16, Chris Angelico wrote:
On Thu, May 17, 2018 at 5:21 PM, Anthony Flury via Python-Dev
wrote:
Victor,
Thanks for the link, but to be honest it will just confuse people - neither
the link
d.
The denial of service is more likely to occur with strings as keys,
than with integers.
See the following link for more information:
http://python-security.readthedocs.io/vuln/cve-2012-1150_hash_dos.html
Victor
2018-05-16 17:48 GMT-04:00 Anthony Flury via Python-Dev :
This may be known but I w
frequently as hash keys - but
I would think that tuples are regularly used. Since that their hashes
are not salted does the vulnerability still exist in some form ?.
--
--
Anthony Flury
email : *anthony.fl...@btinternet.com*
Twitter : *@TonyFlury <https://twitter.com/TonyFlury/>*
__
ode under
test which uses a pythonic code structure can't be fully tested fully
using the standard library.
--
Anthony Flury
email : *anthony.fl...@btinternet.com*
Twitter : *@TonyFlury <https://twitter.com/TonyFlury/>*
___
Python-Dev m
x27;t overload
parens in my opinion - we should have a separate operator - doing this
avoids needing to exclude rebinding, and makes such expressions
considerably more useful.
--
Anthony Flury
email : *anthony.fl...@btinternet.com*
Twitter : *@TonyFlury <https://twitter.com/TonyFlury/>
t operator for assignments which return values avoids
the messy potentially multiple level brackets, and means that the
semantics of an operator depends only on that operator and not on syntax
elements before and after it.
--
--
Anthony Flury
email
level - for a beginner the comprehension may well be baffling where as
someone with more skills would understand it - almost intuitively; as
an example: I have been using Python for 7 years - and comprehensions
with more than one for loop still are not intuitive for me, I can't read
them without a
on, and keeping
track of which x is which (especially which x is being used in the
conditional clause) : surely this would be better : [x_item for x_item
in x if x_item]
Your 2nd example makes no sense to me as to the intention of the code -
the re-use of the name x is confusing at best.
nge(5) for y in [f(x)]]
can become :
stuff = [[y := f(x), x/y] for x in range(5)]
So - overall from me a conditional +1 - conditions as above; if they are
not possible then -1 from me.
--
Anthony Flury
email : *anthony.fl...@btinternet.com*
Twitter : *@TonyFlury <https:
Py2.7 change does not need to be rolled forward to Python3 documentation
The two Py3.8 fixes could/should/can ? be backported to earlier versions
These are all trivial with no conflicts with their target branch (or at
least there wasn't when I made the requests).
--
Anthony Flury
a open bug report) into
2.7, and I am keen to understand the planned time-line for those too.
--
Anthony Flury
email : *anthony.fl...@btinternet.com*
Twitter : *@TonyFlury <https://twitter.com/TonyFlury/>*
___
Python-Dev mailing list
Pyth
All,
I submitted two Pull Requests last Sunday, only a few hours after I
signed the CLA.
I understand why the 'Knights who say ni' marked the Pull request as
'CLA Not Signed' Label at the time I submitted the Pull requests, but I
was wondering when the Labels get reset.
How often (if at all
26510
Thanks in advance,
Anthony
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Mon, May 5, 2014 at 4:16 PM, Nick Coghlan wrote:
>
> On 6 May 2014 07:51, "Paul Moore" wrote:
> >
> > On 5 May 2014 22:32, Anthony Tuininga
> wrote:
> > > So my question is: can I safely make use of this "feature"? It has
> remained
>
Thanks. I think I can live with that restriction. :-) I do not read/write
to the same zip file in the same process.
Anthony
On Mon, May 5, 2014 at 4:10 PM, Gregory P. Smith wrote:
>
> On Mon, May 5, 2014 at 2:52 PM, Anthony Tuininga <
> anthony.tuini...@gmail.com> wrote:
>
On Mon, May 5, 2014 at 3:50 PM, Paul Moore wrote:
> On 5 May 2014 22:32, Anthony Tuininga wrote:
> > So my question is: can I safely make use of this "feature"? It has
> remained
> > in place since at least Python 2.6 but I don't want to assume anything.
> &g
ion simply says that it is an installation default and
doesn't specify what that default is.
So my question is: can I safely make use of this "feature"? It has remained
in place since at least Python 2.6 but I don't want to assume anything.
P
I don't find 'major' and 'minor' confusing too. Maybe because it is the
designation used in linux community for years.
On Tue, Jan 10, 2012 at 7:49 PM, Rob Cliffe wrote:
> But "minor version" and "major version" are readily understandable to the
> general reader, e.g. me, whereas "feature relea
Similar outcome as Paul's.
$ python3 t32enc.py
$ python t32enc.py
File "t32enc.py", line 1
SyntaxError: Non-ASCII character '\xc3' in file t32enc.py on line 1, but no
encoding declared; see http://www.python.org/peps/pep-0263.html for details
$ python3 -V
Python 3.2.1a0
$ python -V
Python 2.6.1
ith Jesse, and we shouldn't heap on more TODOs than already
exist. As people
have mentioned here, it will be easy to add Cython support once the system
is up and running.
Be Well
Anthony
> >
> > Stefan
> >
> > _
On Thu, Apr 7, 2011 at 8:29 PM, Jesse Noller wrote:
> On Thu, Apr 7, 2011 at 7:52 PM, Michael Foord
> wrote:
> > On 08/04/2011 00:36, Anthony Scopatz wrote:
> >
> > On Thu, Apr 7, 2011 at 6:11 PM, Michael Foord >
> > wrote:
> >>
> >> On 07/
marks already exist. If the point of the GSoC is to port the PyPy
benchmarks to Python 3, under "Point (3) Porting", might I suggest a slight
revision of the proposal ;)?
Be Well
Anthony
>
> All the best,
>
> Michael
>
>
> I actually agree with Micheal. I think th
I actually agree with Micheal. I think the onus of getting the benchmarks
working on every platform is the
onus of that interpreter's community.
The benchmarking framework that is being developed as part of GSoC should be
agile enough to add and
drop projects over time and be able to make
day (summer).
Thanks for your consideration.
Be Well
Anthony
> 2. Implementing the benchmark suite. Based on the prior agreed upon
> definition, the suite will be implemented, which means that the
> benchmarks will be merged into a single mercurial repository on
> Bitbucket[5].
>
> 3. P
I strongly urge another release candidate. But then, I am not doing the
work, so take that advice for what it is...
On Oct 14, 2009 10:18 AM, "Barry Warsaw" wrote:
On Oct 13, 2009, at 6:10 PM, Martin v. Löwis wrote: >> I always thought that
the idea of a release ...
No, but let's do one anyway!
e to
> what need fixing up going from beta to beta to rc.
>
> Oh and I'm not going to try and make a version of PyCXX that works
> on 2.x and 3.x as the changes are too fundamental.
>
> Barry
>
> ___
> Python-Dev mai
o turn the slides into a series of articles.
Right now, there's the What's New In Python 3.0, and the PEPs. The
former isn't complete yet (obviously) and isn't all that detailed. The
latter is a whole pile of text, some relevant and some not so much.
Anthony
On Wed, Aug 13,
consider using ctypes.
So yes, collecting this information, even if it's just in a wiki page,
would be a good and popular thing.
Anthony
(*) slides:
http://www.interlink.com.au/anthony/tech/talks/OSCON2008/porting3.pdf
On Mon, Jul 21, 2008 at 2:37 PM, Lennart Regebro <[EMAIL PROTECTED
ow paid sys admin type roles, or are based in
London.
Cheers,
--
Anthony Roy
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
; Neal Norwitz and Ralf Grosse-Kunstleve have access to that
> machine.
Neal's on leave all this month, I believe.
--
Anthony Baxter, ekit. [EMAIL PROTECTED] (03) 9674 7015
Level 3 The Teahouse, 28 Clarendon St, Sth Melbourne Australia 3205
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?
*wave* Hi Barry.
--
Anthony Baxter, ekit. [EMAIL PROTECTED] (03) 9674 7015
Level 3 The Teahouse, 28 Claren
f>-- cPython,
> not such much.
We don't break down "major" or "minor" features, but according to
the What's New In Python 2.5 doc:
> A search through the
> SVN change logs finds there were 353 patches applied and 458 bugs
> fixed between Pyt
, I
> am entirely opposed to any use of JavaScript.
What about flash, instead, then?
/ducks
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
Python-Dev@python.org
fix releases
- only one maintenance branch (most recent) for the bugfix releases
- the last bugfix release of the previous release after a new major
release.
I'm OK with these being formalised - but any additional requirements
I'd like to discuss first :-)
Anthony
--
Anthony Baxter
tions?
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailma
Ok, things seem to be OK. So the release25-maint branch is unfrozen.
Go crazy. Well, a little bit crazy.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
clude:
Bug fixes. According to the release notes, at least 150
have been fixed.
Highlights of the previous major Python release (2.5) are
available from the Python 2.5 page, at
http://www.python.org/2.5/highlights.html
Enjoy this release,
Anthony
Anthony Baxter
[EMAIL PROTECTED]
Python Re
x27;t strike me as critical enough to need
that - and I'm not happy to do the release and just hope. I'll roll
them all back.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
g/2.5/highlights.html
Enjoy this release,
Anthony
Anthony Baxter
[EMAIL PROTECTED]
Python Release Manager
(on behalf of the entire python-dev team)
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
blem,
> > eliminating some segfaults, and fixing some exception code)?
>
> No, the release binaries are all produced, and just await upload.
Apologies for the delay in the uploading - some stuff came up over
the Easter break, and then the website wouldn't rebuild (David and
A
n!
Thanks,
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/m
addressed
(well, to "Python Contributors"), which is a step ahead of most of
them.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
Python-Dev@python.org
http://m
of the data for each transfer.
>
> I agree. I withdrew my original "multimedia library" idea and
> submitted a proposal for the creation of two standard Image and
> Sound classes.
Ideally you'd hook this into the standard library's existing sound
file handli
I'm moving house today and tomorrow, and don't expect to have
internet access connected up at home til sometime next week. In the
meantime, if there's urgent 2.5.1 related issues, bear with me, as
I'll only be on email during the working day. cc Neal (hi Neal :)
is the best bet. Also, the cygwi
this,
I can't remember if you were one of these). My standard response to
this is that people who really feel like this are welcome to pick a
release, say, 2.3, and take on the process of backporting the
relevant bugfixes back to that release, and cutting new releases,
&c.
--
Anthon
ink anyone would mind. There is (as Martin also stated)
zero chance that I will do this additional work. It scratches no
itches for me, and has the potential to add an enormous amount to
my workload of doing a new release.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]&g
x in any way shape or
form.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
e specific version this
problem would go away.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-d
quot; but hell, there's a lot of
different components that make up Python. That would be a
maintenance and management nightmare.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing l
pen as a possibility for a future PEP.
A good first step would be to contribute something like this to the
Python Cookbook, if it isn't already there.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
On Thursday 15 February 2007 21:48, Steve Holden wrote:
> Greg Ewing wrote:
> > Steve Holden wrote:
> >> A further data point is that modern machines seem to give
> >> timing variabilities due to CPU temperature variations even if
> >> you always eat exactly the same thing.
> >
> > Oh, great. Now w
s()/items(). The globals() and
locals() builtins also provide an alternate view with "different
notation to access it". Since you're creating the view explicitly,
I really don't see the problem - any more than say, creating a set
from a list, or a dict from a list, or the like.
t, either, but it's
there for people who need it.
I again ask for examples of other compelling uses that wouldn't be
better solved by using a dictionary with keys rather than an object
with attributes.
Anthony
___
Python-Dev mailing l
turn in performance on a very
> > marginal feature.
>
> The performance question is important, certainly. Initial
> reaction on python-ideas was that a 1% cost would not count as
> substantial
I'd disagree. Those 1% losses add up, and it takes a heck of a lot
of work to
ax that currently
causes this problem the most) is with webpages and with printed
books with code. Sure, everyone can pick a font for coding that
they can read, but that's not the only way you read code. This is
my issue with the foo.(bar) syntax. The period is far far too small
and easy
On Monday 12 February 2007 18:38, Neil Toronto wrote:
> Anthony Baxter wrote:
> > I have to say that I'm not that impressed by either the 1-arg
> > or 2-arg versions. Someone coming across this syntax for the
> > first time will not have any hints as to what it means - an
I have to say that I'm not that impressed by either the 1-arg or
2-arg versions. Someone coming across this syntax for the first
time will not have any hints as to what it means - and worse, it
looks like a syntax error to me. -1 from me.
___
Python-De
.py script that builds the releases does
a "touch" on the relevant files to make sure that make gets the
build right. We had bugs opened at one point because the timestamps
meant you needed a python interpreter to build python.
I'm not _too_ stressed i
can always make 2.6 warn about
the floatobject's __mod__ function being called if the -W py3k
option is on, that gets us part of the way there. And if we have
a "-3" option or the like that also turns on maximum 3.x compat,
that will enable true division, producing the warning.
add "except a as b" to 2.6 - we're just not
ripping out the old way of doing it.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
Pytho
On Wednesday 17 January 2007 05:52, James Y Knight wrote:
> Yes, this is it. As a refinement: if the New Way can easily be
> backported to 2.5,
Um - 2.5 is _done_. Released. In maintenance mode. New features will
not be getting backported to a 2.5.x release.
Anthony
--
Anthony
idea (in another email) of trying to look up
globals would probably cause a horrible performance issue, but it
may be possible to do _something_ clever.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
on't see a path forward that doesn't involve something painful,
so long as 3.0 is going to be the clean break. As I mentioned,
though, I'd like as far as possible to make it so that 2.6 (with a
flag) can be at least vaguely compatible with 3.0.
Anthony
--
Anthony
de does not have to entail dulling the trusty old blade.
I completely disagree here. We cannot simply ignore 3.0 in the 2.x
series. We need to provide (as much as possible) an upgrade path
for people who write and use code in the language.
Anthony
--
Antho
changed raise A, B into raise A(B)
applied to the trunk. This makes it much easier to apply patches to
both the 3.0 branch and the trunk. Similar changes should be
applied to remove, for instance, use of <> and dict.has_key from
the stdlib. Simply put, I'd like the stdlib between 2 and 3
ad.
Checking a single C global int is hardly going to make a huge impact
at all.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pytho
On Thursday 11 January 2007 07:48, Thomas Wouters wrote:
> They serve a different purpose, and it isn't taking any time away
> from me (or Anthony, I can confidently guess) working on 2to3.
Correct. Note that checking for something like dict.has_key is going
to be far far more re
C code modules use the same functions.
There's other changes that are probably too hard to warn about,
because there's not an easy replacement - the exec and print
statements come to mind here.
Comments? What else should get warnings?
Anthony
___
On Friday 05 January 2007 17:40, Gregory P. Smith wrote:
> Whoever is subscribed to python-dev with a broken corporate
> autoresponder that sends everyone who posts to the list this
> useless response multiple times please unsubscribe yourself. Its
> highly annoying and entirely useless since its
otocol
> stacks before which can be leveraged from.
This should go to python-list@python.org (aka comp.lang.python), not
this list. This list is for development _of_ python, not
development _in_ python.
Thanks,
Anthony
___
Python-Dev mailing list
Pyt
On Sunday 24 December 2006 00:19, Andrew MacIntyre wrote:
> Of course, if the project management decide that even the EMX
> support should be removed from the official tree - so be it; I
> will just have to maintain the port outside the official tree.
I feel that so long as there's an active maint
Hi all,
I have a patch for the fileinput.FileInput class, adding a parameter
to the __init__ method called write_mode in order to specify the write
mode when using the class with the inplace parameter set to True.
Before I submit the patch, I've added a test to the test module, and
noticed that t
LSB,
> actually.
Well, I don't know what sort of public statement you want to issue,
but will this do? (Wearing my release manager hat)
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
__
hon. It's worth noting that the entirety
of the Python stdlib is a required package, so it doesn't cause
issues.)
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing
or 2.6. note that read
I agree that a warning seems best. If someone (for whatever reason) is
flinging floats around where they actually meant to have ints, going straight
to an error from silently truncating and accepting it seems a little bit
harsh.
Anthony
--
Anthony Baxter <[EMAIL P
On Friday 10 November 2006 13:45, A.M. Kuchling wrote:
> OK, I'll backport it; thanks!
>
> (It's not fixing a frequent data-loss problem -- the patch just
> assures that when flush() or close() returns, data is more likely to
> have been written to disk and be safe after a subsequent system
> crash
ails. I'm happy for it to go into release25-maint (particularly because
the consequences of the bug are so dire).
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev maili
uilding is a tiny part of the problem... or am I missing something?
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org
completely appropriate, too.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
known issues, please see:
http://www.python.org/2.3.6
Highlights of this new release include:
- A fix for PSF-2006-001, a bug in repr() for unicode strings
on UCS-4 (wide unicode) builds.
- Two other, less critical, security fixes.
Enjoy this release,
Anthony
Anthony Baxter
[EMAIL PROTECTED]
P
.
This solution doesn't require changes to the buildslave code at all - only to
the buildmaster and to regrtest.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
Py
rity related bugs) will get a new release, and then
only with the serious bugfixes applied.
One active maintenance branch is quite enough to deal with, IMHO.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
ease notes, and known issues, please see:
http://www.python.org/2.3.6
Highlights of this new release include:
- A fix for PSF-2006-001, a bug in repr() for unicode strings
on UCS-4 (wide unicode) builds.
- Two other, less critical, security fixes.
Enjoy this release,
Anthony
Anthony Baxter
Thanks to the folks involved in this prcocess - I'm looking forward to getting
the hell away from SF's bug tracker. :-)
Anthony
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscr
tion becomes better understood.
Anyway, all of the above is open to disagreement or other opinions - if you
have them, let me know.
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev maili
strings on UCS-4 (wide unicode) builds.
Enjoy this release,
Anthony
Anthony Baxter
[EMAIL PROTECTED]
Python Release Manager
(on behalf of the entire python-dev team)
pgpHQFKzDQCYF.pgp
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@pyt
he http version that was down)
Anthony
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Wednesday 18 October 2006 00:59, Grig Gheorghiu wrote:
> FYI -- can't do svn checkouts/updates from the trunk at this point.
>
> starting svn operation
> svn update --revision HEAD
> in dir /home/twistbot/pybot/trunk.gheorghiu-x86/build (timeout 1200 secs)
> svn: PROPFIND request failed on '/pr
edge wants to review that it can
be checked in. It _should_ be good, and probably needs to be applied to
release25-maint and the trunk as well.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
u're willing to
> coordinate, is there anything we can do to help?
Less than a normal release, since I'm not going to worry about changing the
docs, the windows installers or the mac installers. I'll look at it next
week, once 2.4.4 final is done.
Anthony
--
Anthony Baxter
On Tuesday 17 October 2006 18:54, Fredrik Lundh wrote:
> Martin v. L�wis wrote:
> > In 2.3.6, there wouldn't just be that change, but also a few other
> > changes that have been collected, some relevant for Windows as well
>
> why not just do a "2.3.5+security" source release, and leave the rest to
releases having new capabilities.
Since it wasn't possible in earlier than 2.5 either, I'd say it's on the
edge of being a bugfix. Let's be conservative and not backport it, since it's
also a pretty marginal feature.
Anthony
--
such as the release
> >>team by allowing everything necessary to be generated from a simple set
> >>of data that wouldn't be difficult to maintain. Anthony has enough on
> >>his plate without having to fight the web server too ...
> >
> > There is alw
ne, macteagle. For some reason builds fail on it right now - Ronald
might be able to supply more details as to why.
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
have to have an overall infrastructure that lets you make
> incremental tweaks to the tool chain, so things can get a little better
> all the time. Pyramid obviously isn't such a system.
I can't disagree with this.
--
Anthony Baxter <[EMAIL PROTECTED]>
It'
ry, as an HTML fragment. click "save" to publish.
>
> 3) mail out an announcement when everything looks good.
>
> Maybe I should offer Anthony to do the releases via effbot.org instead?
First off - I'm not going to be posting 10M or 16M files through a
web-browser. That&#x
> portable code at all.
"One" might say that. I wouldn't. It stays out until 2.6.
Sorry
Anthony
--
Anthony Baxter <[EMAIL PROTECTED]>
It's never too late to have a happy childhood.
___
Python-Dev mailing list
1 - 100 of 377 matches
Mail list logo
