27;hg email' to send the
patch as well.
Once the migration is done, of course, users who have been working with
that mirror will need to set up new clones for the upstream and re-clone
the working trees, as the revision IDs won't match, etc.
Tres.
- --
ndred megabytes, more or less?
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG
do "familiarization" drills with
the majority of mercurial's features, with the exception of the final push.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excelle
Python modules /
scripts ever written: the 'string.printable' set, less formfeed and
vertical tab, is 98 characters long.
> That's why I'm advocating a dedicated flag instead.
+1.
Tres.
- --
===
Tres
et, with
user-visible forks to known fixes, etc., it would get "caught up" to
people's expectations.
Perhaps I'm really suggesting that there be an 'idle2' project nn
bitbucket, as a "friendly fork" of the mostly freeze-dried version in
stdlib.
Tres.
- --
==
sely
this reason. Third-party code which relies on 'hasattr' to mask
non-AttributeErrors is broken alreay (it just doesn't show the borkedness).
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palla
hink taking this opportunity to use "real" version IDs for tags would
be a much better than sticking with the old cruft.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Sof
se). Given that fact, and
PJEs assurances, I think amending the PEP and then immediately declaring
it final is reasonable.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://p
l). Although I would
prefer 'c' over 'rc' in the normalized case, PEP 386 allows 'rc' as an
alternative to 'c' precisely because some Python versions used it). I
think we need to make the migrated version tags match the corresponding
tarball versio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/29/2010 08:38 AM, Benjamin Peterson wrote:
> 2010/9/29 Tres Seaver :
>> +1 for bare release numbers (Dirkjan's proposal). Although I would
>> prefer 'c' over 'rc' in the normalized case, PEP 38
hat
> indicates some outage. I'm still unsure what "it" is that was happening,
> so it's also difficult to analyse this further.
FWIW, PyPI was inaccessible for some longish period of time this morning.
Tres.
- --
=
d cause
apparent outages from the outside viewer's perspective, without
necessarily leaving any trace on the machines hosting the sites, except
a drop in traffic in the logs.
Tres
- --
=======
Tres Seaver +1 540-429-0999
sm be spent on making Python 3 rock, and in
> porting third party code to Python 3.
Sure you would -- you're already invested there. I would like to be
there, but can't take off the several months required to port the whole
stack under my own code.
Tres.
- --
=
in making it happen, so a new crop of
> developers will need to step up if it is going to become more than a
> CCP-specific 2.x fork.
Thanks for the helpful guidance to such prospective volunteers!
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion S
python-dev. If a new
retro-fork development community emerges, its members will include folks
who have a vested interest in continuing Python 2.x development, and
hence can donate (or recruit) such in-kind contributions.
Tres.
- --
==
release the improved
> libraries for everything from Python 2.4 and forwards if you like.
>
> So it can be done, but the question is "Why?"
The OP has existing patches to contribute which the core python-dev team
consider "not-a-bugfix", and hence not acceptable for the
es, should be fish-slapped. ;)
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http:/
_bar import __all__
I guess the usual caveats apply for dopplegangers / proxies. ;)
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE--
):
...
# Replace with accelearated C implemenataion
try:
import _spam
except ImportError:
pass # accelerated version not available
else:
foo = _spam.foo
bar = _spam.bar
- --- $< -
This explicit name remapping catches unintentional
he set of applications /
modules which both use the undocumented names *and* do so via 'import *'
can be safely deemed "too small to worry about".
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software &
is way even though the changes to PEP 333
were essentially clarifications which applied only to Python 3: the
existing Python 2 semantics would have rmeained the same.[2]
[1] http://permalink.gmane.org/gmane.comp.python.devel/117269
[2] http://permalink.gmane.org/gmane.comp.python.devel/117249
Tres.
- --
==
of today.
>
> B) Remove the DeprecationWarning, simply document that people should be
> explicit about it if they care at all and that the default will change in
> 3.3.
>
> C) Never change close_fds behavior. we're stuck with it for life.
>
> D) Deprecate close_fds
eprecationWarnings is bad housekeeping / "broken window" stuff: it
leads application developers to ignore them.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Softwa
tc. operations (it does this by default during
'export', which is likekt why the tarball process works):
http://svnbook.red-bean.com/en/1.1/ch07.html
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@
build hang around until
> the next build takes place. They can however, interfere with the svn
> checkout so things never get to the point of using kill_python. So
> maybe kill_python's use should be moved to the clean stage?
Maybe belt-and-suspenders it in both places.
Tres.
- --
f like logging, which should only go to
stderr. Much better to document the "how-to" for setting up something
like that than to make it a default.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@p
uch cases,
with the closing paren on the following line, so that adding or removing
an argument at the end of the list stays consistent (the diffs are
better, too, when I use this pattern).
Tres.
- --
===
Tres Seaver
e bytes type and use os.environb instead.
I'm not clear on the semantics here, but I'm pretty sure you'll find
that the web-SIG does know them well. I have CC'ed that list (via gmane).
Note that Guido just recently wrote on that list that he considers that
PEP to be de facto a
py empty of anything but the __path__-munging majyk /
boilerplate is required to make such installs work regardless of the
order of PYTHONPATH.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Pa
requests" for that fork instaed.
For the repoze and pylons projects, we have found the quality and
quantity of patches went up *significantly* when we made it easy for
somebody who doesn't work on the code all the time to use this workflow
(fork to a public repo, clone, hack, commit, push, request a pull).
Tres.
- --
==
dbots help the visibility of changes being landed to
the language or standard library?
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
--
les are a huge anomaly
ISTM that other cases (version of a spec targeted by the module, or of
the underlying C library it wraps), need their own attribute.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladio
ke down.
The "push race" problem in hg definitely bit us at PyCon this year while
sprinting to get WebOb's test coverage to 100% (preparing for the
Python3 port). I haven't seen that issue so much with git or bzr, but I
may not have used them in such a race-friendly
y a changeset in my local line of development, and by a side
> branch in the mainline DAG once my merge is completed. You might want to dig
> into that sideline to see if indeed I addressed the issues in your second
> review of my code. If we have to manually collapse changesets
or the stdlib (maybe during
build?), and add support for running tests of a named module and its
dependents. Any non-documentation change to a stdlib module requires
running this new kind of test against that module.
Tres.
- --
==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/23/2011 09:36 PM, Stephen J. Turnbull wrote:
> Tres Seaver writes:
>
> > On 03/23/2011 01:24 PM, Antoine Pitrou wrote:
> > > On Wed, 23 Mar 2011 10:25:01 -0700
> > > Ethan Furman wrote:
> > >>
built during
an intial full run of the suite.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/26/2011 02:56 AM, Stephen J. Turnbull wrote:
> Tres Seaver writes:
>
> > That was precisely my proposal:
>
> Sorry about that. I live in a disaster area, and was limited to
> GMail until two days ago, and lost a fair amo
557), I hope that the
> situation will be better in a few hours.
>
> Thank you Antoine for your reviews!
Thanks very much for you hard work on this cool new feature.
Tres.
- --
===
Tres Seaver +1 540-429-0999
le) on the pure Python version?
>
> Let's say "as good coverage as the C code has", instead ;)
The point is to require that the *Python* version be the "reference
implementation", which means that the tests should be fully covering it
(especially for any no
t; Cython is out of scope for this.
Why is it out of scope to use the benchmarks and test harness to answer
questions like "can we use Cython to provide optional optimizations for
the stdlib"? I can certainly see value in havng an objective way to
compare the macro benchmark performance o
SoC effort, just not for perf.python.org as a whole.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/
like you are missing a bunch of development headers on the system
(at the time Python's 'configure' was run). E.g., on a Debian system,
$ sudo apt-get install zlib1g-dev libbz-dev libreadline-dev # etc
Tres.
- --
=======
e challenged.
Trying to accelerate existing code which doesn't have the coverage is
insane: how can you know that the accelerator doesn't subtly change the
semantics without tests?
Tres.
- --
===
Tres Seaver +1 540-429
> Can't this work be done in the branch of main repo, so that everybody
> can track the progress in place? Is there any picture of the process
> similar to http://nvie.com/posts/a-successful-git-branching-model/ ?
Note that in that writeup, 'release-*' (and 'hotfix
or remotely-exploitable
WP bugs:
http://www.wordpressexploit.com/
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: Gnu
l be made available
>> on PyPI under the +name :mod:`distutils2`.
>
> Even for Python 2.4, really? Do you really need to support this old Python
Yes. Many projects distribute packages to folks still using 2.4.
Tres.
- --
=======
nd
therefore bound via descriptor semantics? In this sense, 'staticmethod'
doesn't create a "method" at all -- it just defeats the default creation
of a method-yielding descriptor.
Tres.
- --
===
Tres Seave
#x27;t include 'b') ?
>
> +1.
>
>> That'll make it compatible to the Py2 world again and avoid
>> all the encoding guessing.
>
> Yep.
+1 from me, as well: "in the face of ambiguity, refuse the temptation
sto guess."
Tres.
- --
==
: they are in fact the
"canonical" repository locations, even if most of the work is done in hg
and patched into them.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software &q
he build after updating an underlying system library.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGN
sion of Python supported by
the library (Python 2.3+, AFAICT).
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.
g_resources' constraints.
- Unpack the source distribution to a temp directory.
- cd into that directory and use sys.executable to invoke
'setup.py install'. Any extra command-line arguments beyond those
used to find the source distribution would be passed on to the
'
estricted, and thererfore introspectable, configuration-driven
approoach seems much cleaner.
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design"
ld it locally.
> But if these problems are solved, then I have no problem with seeing
> the features of setuptools added to the standard library - resource
> APIs, plugin/entry point APIs, ways to create executable scripts, and
> such things *should* be standardised. Dependency reso
n such packages, and make a
tool which actually works for the huge majority of distributions which
don't need to do more than install files.
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design"
erable.
For a long-running Python application (as opposed to desktop tools or
scripts), installing a custom Python is the "safest" choice: it
insulates the application not only from unexpected system-driven
site-packages changes, but also allows greater control over other Python
configu
g out the .pyc files and carefully removing aliased
imports eventually got the problem to go away (at which point I could no
longer reproduce it at all).
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
70 fail*.
>
> Twisted: 6149 assert* vs. 1666 fail*.
>
> paramiko: 431 assert* vs. 4 fail*.
>
> The data seems pretty overwhelmingly in favour of keeping assert*.
FWIW: Zope2: 16878 'assert*', 2892 'fail*'. I would keep both by
preference, rather than insist
pain, write a *new* module,
'unittest2', and port Python's tests to use it, thereby leaving the much
larger volume of not-in-Python tests still working. One might then
remove the 'unittest' module in a later release, packaging it as a
standalone distibution for the proje
or old code to continue working by adding
> the old unittest module on sys.path.
>
> Please note that the required renaming of the methods in existing
> tests is not going to be as straight forward as you may think,
> since you may well rename method calls into the tested application
poent wants to be able to make
further assertions about the raised exception (e.g., to test its message).
Tres.
- --
=======
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design"
te. I'm willing to bet that *nobody* who is still using it would
be surprised if they had to recode it when upgrading to a recent Zope,
so maybe we can just change the trunk without worrying about it.
Tres.
- --
=======
Tres Seaver
he same error as below?]
>
> | test test_sys failed -- Traceback (most recent call last):
> | File "...\subprocess.py", line 817, in _execute_child
> |startupinfo)
> | TypeError: environment can only contain strings
That definitely shouldn't happen
it were removed?
- -1. The feature exists to allow adherence to PEP-8, "Limit all lines to
a maximum of 79 characters.", without requiring runtime concatenation
costs. I use it frequently when assembling and testing message strings,
for instance.
Tres.
- --
===
>
> If linking to the new version could be done easily, we could as well directly
> redirect. The problem is that having that mapping in the first place is hard.
Why would you remove the old docs (ones with 2.5 in the URL)? They
still provide value for folks who can't yet move to 2.6 /
t_buffer:
return 1
elif len(self.producer_fifo):
p = self.producer_fifo.first()
if hasattr (p, 'stalled'):
return not p.stalled()
else:
return 1
Tres.
- --
===
Tres Seav
().
Under this culture / pattern, one would tag the release, then modify the
version on the quasi-tag branch, rather than committing the released
version of setup.py to the source branch, only to follow it immediately
with another commit reverting the release-specific change.
Tres.
- --
==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Georg Brandl wrote:
> Stephen J. Turnbull schrieb:
>> Tres Seaver writes:
>>
>> > svn doesn't have any true tags, AFAIK: everything is a branch.
>>
>> Yow! I couldn't have imagined that would be tr
ing.
Given the choice, I would move the ssh / svn docs *out* of the FAQ into
your document, leaving pointers to the new sections behind.
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladi
ed in 2.5 but not
> yet in 2.4. this would include
>
> CVE-2007-4965
> CVE-2008-1679
> CVE-2008-1721
> CVE-2008-2315
> CVE-2008-3144
> CVE-2008-1887
> CVE-2008-4864
+1 from a non-core developer who still has to keep sites using 2.4 up
and running.
Tres.
- --
=
nheritance-based: it means replacing a method
/ attribute of a module or class from a different module, after import time.
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excell
;whiz bang"[1] in my book.
[1] http://www.merriam-webster.com/dictionary/whizbang
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNAT
and allow more sophisticated applications to handle it.
Amen! the idea that paths, environment varioables, and stuff pulled off
of sockets can be treated as text rather than strings is just wishful
thinking.
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PRO
t place?
My guess is that Luke wants to cross-compile bdist-win distributions for
the benefit of tool-deprived Windows users.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software &quo
blem...
It barfs on Macs as well: indeed, it is worse, because the connection
just fails there, rather than trying IPv6 and then falling back to IPv4.
For instance, tunneling a connection over SSH to a Mac box via '-L
:localhost:' will fail to connect at all, unless the server
TW, there is already an "until" keyword in python, it's called "while not" ;)
'until' is used at least in some languages (Pascal, Modula*, maybe Ada?)
for a "terminate at bottom" loop (one guaranteed to run at least once):
in such cases, the predicat
ity to
> road test the functools patch by using it to refactor pprint and check
> the performance implications)
/me wonders about the performance-criticality of anything using
'pprint'. Or were you just planning to use it as a means to benchmark
the 'simplegeneric' stuf
- %< -
So, the OP's use case *could* be satisfied, assuming that the Py3K
version of urllib sprouted a means of leveraging that header. In this
sense, fetching the resource over HTTP is *better* than loading it from
a file: information about the chara
full character. I'm sure Spanish
> keyboards have a better way than that :-))
FWIW, I was taught that Spanish had 30 letters in the alfabeto: the
'ñ', plus 'ch', 'll', and 'rr' were all considered distinct characters.
Kids-these-days'ly,
Tres.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/01/2011 11:59 PM, Stephen J. Turnbull wrote:
> Tres Seaver writes:
>
>> FWIW, I was taught that Spanish had 30 letters in the alfabeto:
>> the 'ñ', plus 'ch', 'll', and 'rr' were all
ention this abbreviation?
FWIW, the RFC 20 (the ASCII spec) really really defines 'NUL' as the
*name* of the \0 character, not just an "abbreviation used in tables":
http://tools.ietf.org/html/rfc20#section-5.2
Tres.
- --
==
t;replaces" dead batteries. :)
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version
e with a completely
> unrelated meaning. :-(
One could always think of the Midwest US farm country, cut into even
one-mile sections by dirt roads, and think of 'grange'. :)
Tres.
- --
===
Tres Seaver +1 540-429-09
ve braces everywhere?
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG wit
adjacent to that. Does
> that seem like a better solution? Can anyone suggest better
> alternatives? Sorry if this has come up before and I've missed
> something obvious.
+1 to making it a package and keeping the data in the package.
- -1 to a zip file: each scripts should b
s users are the only ones who routinely don't have access to a
compiler at all. Even trying to push binary distributeions to PyPI
for Linux is a nightmare (e.g., due to UCS2 / UCS4 incompatibility).
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea.
can work on this.
I would say this is a perfect "opportunity to delegate," in this case
to the devotees of other cults^Wshells than bash.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@pallad
cly,
>
> Oh, come on, surely this doesn't effect the casual reader?
/me presumes an ironic mispeling there. ;)
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by De
n is more practical than the options that are already there.
The "redundant" u'*' spelling would be present in Python3 for the same
reason that the equally-reduntant b'*' spelling is present in Python
2.6+: it makes writing portable code simpler.
Tres.
- --
==
process of getting that package's unit test coverage up
to snuff before ripping out the 2to3 support in favor of a subset).
Using 2to3 during ongoing development makes Python feel like Java/C++,
where "get a cup of coffee while we rebuild the world" is a frequent
occurence.
Tres.
rough and edit every
> single one of his commits to add them.
FWIW, +1 to mandating braces-always (even for one liners): the future
maintenance burden isn't worth the trouble of the exception. In the days
when I did C / C++ / Java coding as my main gig, braceless code was
routinely a b
s a dict to hold the form / query string data being supplied
by untrusted external users.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"
urely hypothetical, while the second set
is *lots* of deployed applications.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
undersand you. In POSIX land, the only thing which
changes the mtime of a directory is linking / unlinking / renaming a
file: changes to individual files aren't detectable by examining their
containing directory's stat().
Tres.
- --
=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/2012 04:42 PM, Brett Cannon wrote:
> On Fri, Feb 10, 2012 at 16:29, Tres Seaver
> wrote:
>
>> On 02/10/2012 03:38 PM, Brett Cannon wrote:
>>> Changes in any fashion to the directory. Do filesystems
>>>
EP addresses one of the last remaining issues to making
such codebases clean and easy to maintain (the sys.exec_info hack is not
needed in Python >= 2.6).
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Pall
;, "credits" or "license" for more information.
>>> ({},)
({},)
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP S
change
> would spawn such a great discussion. After all what we're discussing
> here is the introduction of one letter to literals :-)
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladi
f Zope-based sites in production, including very
high-profile ones: http://plone.org/support/sites
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"
201 - 300 of 333 matches
Mail list logo
