e that an error has occurred.
Another aspect of bare except (IME) is that they are used when you
want to do some work, but continue to propagate the exception upwards
via a bare raise. E.g. rolling back a transaction, or as you
mention, logging the error and continuing.
- -Barry
-
can't (easily) get any other way.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRY9eMXEjvBPtnXfVAQJjIQP9Ei/KayIeuU3CAkPKsSFKw43v1sscMOP4
Y7BaUWbRlwptj4k4T2spm0leFneUoOl513B+Vyz/hZps9Zd2ltOo7NtBTqmGQ02P
jAK6wcRkjgXJDjvZo2YWbabZLy97vCX1/GHGKbnLGlB6w6t3bI
object it returns.
>
> If we want to make the seek API more 21st century, why not use keyword
> arguments?
Or put the constants on class attributes.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRZWRM3EjvBPtnXfVAQLWdwQAmrt5ncAhFIxCK2Tm72g
stness of the
> Python installations.
Sometimes though you want to do this, as when you want your
application to ensure it gets a particular version of a standard
library module, regardless of the version of Python being used. And
now we're back to application-specific site-packa
What makes it more complicated is when you have dozens of entry
points (read: command line scripts), but it's solvable.
I guess when I read "PYTHONPATH" I also read "sys.path", so now that
I've slept a little, never mind!
- -Barry
-BEGIN PGP SIGNATURE-
But if you go with a header prefix, then the shorter
"py_" is fine.
FWIW, I tried to do a quick grep around some of our code and I found
that the only "internal" header we include is structmember.h. Why is
that not part of Python.h again?
- -Barry
-BEGIN PGP SIGN
ove everything else into a
'python' subdirectory.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRZ0pfnEjvBPtnXfVAQKuyAP+J8Tm3z4am5BOfXCSJIeHsA1tEddeniuM
dqSUAPUQUag9WkvkAreQYXu3iRC26e52mJ0B8eceqiuBa16WPILb0CvRFCBoW2fc
/FAg4EROlMBhrE/MWVSfGSi76bL+4CwaogmHOnsvyCDEpp
and would even allow users to use the python framework as a
> normal framework.
I think that's basically correct: framework includes are searched
after normal includes. You might be able to confuse things if you
used -F/-framework options, because I believe those are interleaved
ps?
I think I found the offending address, which I won't name on this
mailing list. I have disabled the address so please let me know if
you continue to see the autoresponses so that we can either rejoice
or I can re-enable the poor guy and we can all continue to despair.
- -Barry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 5, 2007, at 9:29 AM, Barry Warsaw wrote:
> On Jan 5, 2007, at 6:06 AM, Anthony Baxter wrote:
>
>> On Friday 05 January 2007 17:40, Gregory P. Smith wrote:
>>> Whoever is subscribed to python-dev with a broken corporate
&
t
programmatically, which was an absolute requirement for us, since
none of the extension modules were importable unless epydoc was run
inside the embedded environment. I got it to work, but it was a bit
of a pain.
If you've already explained it, that's fine, but if not, could you
o
code
still has a few lurking backticks), but I might balk if that slope
gets any more slippery.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRaVFinEjvBPtnXfVAQJKYgQAg3RjH5OPF9TkdtWHqp9ylwnsRaBwuUdI
MGSD5ukkddl7XuluHMxVDIduxxTrQos9bCacLPtK5YejhxKnXU0V8jfDYyXv1pDB
j+D
sense for all 3xxx PEPs to include a discussion section
on porting.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRael9nEjvBPtnXfVAQIqRQP+PrYnz/XSnGsplGj1+/MtBFzkbKeZEEn7
tN1NyKNZ7Rt7w+K9JhO9D1XismB3Wwwd66d7+N8vY/y/ea/cMosUwYS7LbwTmvcV
MX3H
hat view thingie have an __call__ that returned
the backward compatible list object?
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRa1V9nEjvBPtnXfVAQIODQQAlCI4iykl93zKJeIW/3QuuOm4jCRrhffV
BOkuu+mM4N/1Rqc2TCBHUIi995TkYo/6Wuzb7LrXweG5kLm2cdWTNm+aSgZq35
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 31, 2007, at 10:11 AM, Aahz wrote:
> Thanks again for giving me something fun to do with my life. ;-)
Here, here!
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRcC0nnEjvBPtnXfVAQI2+AP/QcOBB
umped out immediately.
> (When do you ever see self[anything]?)
Raymond's -> suggestion was nice.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRdEIB3EjvBPtnXfVAQLENQP+KlLGE0rldGbOdpeMdsZ6dX7ga9Fb2mZR
wkOIEYJW6H8n6OyzawPgkvQWpuJzUlC+5A42gxYUdkC4
tated, but I
echo Greg's sentiment.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRdJaynEjvBPtnXfVAQJHuQP7B7FlA5wO28dEW62q3VSOr7iUm/6FLZ/6
hoXq47S1F/Yre0bl9p1C2bOCAXeBNXoQC55oPw4a4XUC3C2G/Pf3TJnlOZ0u1M7y
5Ug8MbDxf8SvHl3efZSOjvx2S8OPv0m11teP+d9l11upXz7ASAVlwYZhKRMum
the fan running at constant speed :)
>
> Unless the fans are perfectly balanced, small changes in gravity are
> going to affect the rate at which they spin. So I guess the
> position of the moon will affect it :-)
Except on Tuesdays.
- -Barry
-BEGIN PGP SIGNATURE-
of our big embedded app to Python
2.5, that's (almost) exactly what I did. I didn't add the #define to
a Python header file, but to our own and it worked pretty well,
IIRC. I never went farther than the experimental phase though.
- -
you really do want the #! line to point to the OS's
version of Python rather than whatever random installation is on your
$PATH.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRd8//XEjvBPtnXfVAQLZKQP+NvcjMIT4tCZtOIPWo8Kj1JMp5iX0Nqib
BBXPgDtncJ6VvITcl
aults of whatever Python 2.x version is
out to complete the transition.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBReJgp3EjvBPtnXfVAQIZQgP+K5iWRTYHYvqb3cAUFJw/yDDiz5JPG94x
XdMEnCUXwJVyU30q3FGSNeaz3hwQq7xgJuH5DBRHnGkxp7H/K42ft/KXnJVGnkt4
y number of ways
and still just have this one little branch for this one little feature.
Hope that makes sense! I haven't used a real dvcs for very long, but
I'm starting to see the fundamental improvements to the development
process
So yes, there's some initial overhead
but with bzr done right, for most subsequent work, there's no
perceptible lag due to the scm.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRe2QM3EjvBPtnXfVAQIaSAP/SAoPvqTQZgfG8EDZB6J2hgggAUgWlYun
ove the one-off hack in the
email package for its PEP 8-compliant renaming by using the code in
the reference implementation for PEP 364.
Here's the text of the PEP, which should be available at http://
www.python.org/dev/peps/pep-0364/ shortly.
- -Barry
PEP: 364
Title: Transitioning to
ertain people. I think the term was project leader or some such.
Of course, this didn't mean that someone else couldn't fix the bug or
that the bug couldn't be reassigned to someone else, but at least it
initially gives all issues to the person nominally responsible f
}.
> If you are going to have the object accessible from outside
> sys.path_importer_cache I would also add an attribute that contains
> the magic string used on sys.path.
Of course, that magic string is also available via oldlib._magic. I
tend to think it won't be necessary, but if
it's just a hack to support aliasing an import of one name
(the old name) through the import of another name (the new name).
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRe7p+HEjvBPtnXfVAQKFDQP9HSL0o6mWj4iNMKJNjVy1qcbK1HCHbDVv
JlnqPlegRiZR+KwDhPiGLD8epepuZ3d
available via oldlib._magic. I
>> tend to think it won't be necessary, but if people really want it, I
>> can see putting the magic string as an attribute on the
>> OldStdlibLoader object, e.g. sys.stdlib_remapper.importer_cache_key.
>
> Yeah, that was what I was th
y get loaded when the package gets
imported. Once read I don't think we'd need to stat for those or
read them again.
It would definitely be worth measuring, but my guess is the
additional overhead will be negligible.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG
porting the
pkg.old_names from a .pth file rather than just including whatever is
necessary right in pkg/__init__.py?
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRe9+wHEjvBPtnXfVAQI60AP8D7PFDNVR/BiLEoz8iQKYJUOsd8vtXTF5
lcmDi+L0SZ8N95KxlI2icQmaRk2wNhO+0Djp
lity unless and until the keyword
> parameters are backported.
Let's remember the lessons of True and False in Python 2.2.1.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRfr04nEjvBPtnXfVAQKxXgP
background. While not quite ready yet, I'm also
becoming less certain that some of them should actually go into
2.5.1, rather than waiting for 2.6. A bug day would be a good way to
coordinate with a few other devs and figure stuff like that out.
- -Barry
-BEGIN PGP SIGNATURE
dea! I have a mailbox bug that'd
>> greatly benefit from discussion about how to fix the problem.
>
> How about Sunday, April 1st?
I could probably show up for a few hours that day.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRgGQrn
ect their devs to read it and adhere to it, possibly with
a few local exceptions. It might even be worthwhile to give PEP 8
more exposure in the tutorial or on the documentation ToC page.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (Darwin)
iD8DBQFGFmAl2YZpQepbvXERAs7XAJ9IAjcp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 11, 2007, at 9:15 AM, Kristján Valur Jónsson wrote:
> The SVN repository hasn‘t answered http requests since this
> morning. Anyone know what is up with that?
Known breakage. We're working on it.
- -Barry
-BEGIN PG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 11, 2007, at 10:34 AM, Barry Warsaw wrote:
> On Apr 11, 2007, at 9:15 AM, Kristján Valur Jónsson wrote:
>> The SVN repository hasn‘t answered http requests since this
>> morning. Anyone know what is up with that?
> Know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 11, 2007, at 11:10 AM, Barry Warsaw wrote:
> I'll take this opportunity to mention that we've ordered a new ssl
> cert for our expired one on https. It hasn't arrived yet, but
> should within a few days. I'
n throw an input/output
error.
Disabling debug output is band-aid yes, and any application on the
Mac like the above snippet will still fail. If anybody has any
suggestions, I'm all ears, but I've reached the limit of my pty-fu.
mr-t-says-i-pty-the-fu-ly y'rs,
- -Barry
P.S.
, and any application on the
>> Mac like the above snippet will still fail. If anybody has any
>> suggestions, I'm all ears, but I've reached the limit of my pty-fu.
>>
>
> I don't think this is an OS X PTY bug. Writing to a blocking file
&g
from the master_fd.
You have to wrap the read in a try/except to catch the OSError input/
output error you'll get on Linux when you read past the end of the
buffer and the child process has already exited.
Thanks,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.
#x27;ll back it out and re-apply after 2.5.1 final.
>
> Please back it out. If there are changes to the branch, we would have
> to create another release candidate (IMO).
I see Neal did already... thanks Neal. I was away for most of the
weekend.
Cheers,
- -Barry
-BEGIN P
ease use the absolute package name test.test_support.TestCase.
Remember that some of the code in the stdlib is released externally
to Python (e.g. the email package), so their test suites have to be
runnable in that deployment mode.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Guido> And they should. There really is no excuse for letting one
> Guido> developer's poor choice of tools cause later grief for
> all other
> Guido> developers.
>
> Just a little FYI, python-mode (the one Barry and I manage - dunno
> about the
> one d
ager to get some new blood involved in
the Python community. We may not accept all applicants; we're aiming
for two or three additional editors, but that number isn't set in stone.
Cheers,
- -Barry (and David)
-BEGIN PGP SIGNATURE-
Version: G
ttext). You would either have to teach
pygettext and maybe gettext about this construct, or you'd have to
use something different. Triple quoted strings are probably not so
good because you'd have to still backslash the trailing newlines.
You can'
nts"""
>
> if condition:
> print __doc__
> sys.exit(1)
>
> This way usage immediately stands out much better, without any
> unnecessary new lines.
Me too, all the time.
- -Barry
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 3, 2007, at 10:40 AM, Stephen J. Turnbull wrote:
> Barry Warsaw writes:
>
>> The problem is that
>>
>> _("some string"
>>" and more of it")
>>
>> is not the same as
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 3, 2007, at 12:41 PM, Stephen J. Turnbull wrote:
> Barry Warsaw writes:
>
>> IMO, this is a problem. We can make the Python extraction tool work,
>> but we should still be very careful about breaking 3rd party tools
>&
cessary, patches for earlier releases may be made available, but no
earlier versions are officially supported by the PSF. We do not make
releases of unsupported versions, although patched versions may
become available through other vendors."
- -Barry
P.S. On re-reading this, I realize this
wn for. It's also not that big of a deal if we
amend the policy later because we have volunteer release managers for
earlier versions.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRkTp43EjvBPtnXfVAQJCigP9GtmkyIpI7NadM0pfPIIsLkLCvqFA8sNe
oMVv5cGMtkDaw6x4k
ns if necessary, such as to
fix security problems, but we generally do not make releases of such
unsupported versions. Patch releases of earlier Python versions may
be made available through third parties, including OS vendors."
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG
that security issues should be
reported to security at python dot org instead of public forums or
trackers, so that the Python Security Response Team can take the
appropriate and responsible actions?
- -Barry
[1] I still think we should craft some text for the website, but it
can now be as simple
afe to apply to their package trees.
I don't think rolling out tarballs is all that much additional burden
once everything else is said and done, so I think we should do it. I
don't want to give Anthony more work than he wants to do, but I feel
confident we can find volunteers to
so that
others have experience doing releases too.)
We should decide what's right for security releases and then assess
whether we need to recruit in order to perform that activity the way
we want to.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRkiEFXEjvBPtn
a security
patch, not "months" or "years".)
Also, I would like to document explicit that it is the responsibility
of the PSRT (or its designate) to commit security patches to revision
control. The act of committing these patches is a public event and
has an important impa
> (you can tell that I come from a country where people are quite
> skeptical about the secret service).
There's no secret police here, since almost anyone who's foolish
enough to volunteer to do some work could easily infiltrate that most
cloistered of organizations.
I believ
sents the consensus
of the community, then that's what we'll do.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRkm+ynEjvBPtnXfVAQJW/gQAnzhTEwt9/YCydkRTqI51Z9iAQTikaDpI
/2YMpvv6nxJX7dUoDQam08T8BoZ0Vt2iXFXMQ90GD99nYOevFTKMSx7u4l/kY/Do
U0a4BG8lVaIZUS5ipW/7su
specific proposal? My proposal would be
quite different, and I think, more Pythonic. Should I bother
submitting a PEP?
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRk366XEjvBPtnXfVAQKL1wP8D/iUag8jCCjFTT1Qa+Z1iwFcGCFgHq7c
+ZzR2PrqkG8+2f3MxEa31GM
first step would be to announce the package on
c.l.py.a :). But cool, that tells me what I wanted to know.
Thanks,
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRk39RnEjvBPtnXfVAQJ+BAQAm5oc/gzHq1bcwUt961Rc/9Ga7SX0CQI3
qcpSgQTnUOQxOFgas71tfZ1KC0Hg8ce
m to use
>logging.basicConfig(), the easiest and most straightforward way for him to
>add logging to his application.
+1
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mail
On Dec 08, 2010, at 12:01 AM, Vinay Sajip wrote:
>Barry, if you mean +1 as in "I agree this is how it should work", then
>we're all agreed.
Yep, that's what I meant!
-Barry
signature.asc
Description: PGP signature
___
Pyth
nts have a great weight
>here.
I have used them and I do think they're fairly ugly and unwieldy. However, I
agree that we should not rush into a different design. Since sysconfig was
essentially refactored out of distutils (and now we have two ways to do it!),
and we're getting
ocs, or just an oversight?
It's an oversight. The changes should be accompanied by version* directives.
I see you already committed a change for compileall.rst - thanks for that!
Please feel free to add anything you find missing or submit a bug report and
assign it to me.
-Barry
signature.
On Dec 30, 2010, at 02:50 AM, R. David Murray wrote:
>You are welcome; thanks for the feedback. (I sometimes feel
>like I'm working in a bit of a vacuum, though Barry does chime in
>occasionally...but I do realize that people are busy; that's
>why I inherited this job in
s a sys variable, plus command line
option and/or environment variable?
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/
.
You can download the python-mode.el file or the full tarball from:
https://launchpad.net/python-mode
Bugs can be filed at:
https://bugs.launchpad.net/python-mode
Enjoy,
-Barry
New in version 5.2.0
- Fixed filling of triple-quoted strings.
- Add new font-lock
On Jan 17, 2011, at 12:53 PM, Guido van Rossum wrote:
>Wow, that Purify file is really old... Unless anyone can confirm it
>still works, maybe just toss it? Barry?
Wow indeed. The email address in there hasn't worked in, what? a decade? :)
Toss it!
-Barry
signature.asc
Descr
ther come up with a different status to describe an API PEP
that has been locked down. Re-using Active doesn't seem right to me.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.py
;m not subscribed I
>dunno if it'll make it or not.]
Technically, Pipermail, but jeebus how I hate hacking on that code. :) Although
it's been futile for the last decade, maybe this time will work: volunteers
wanted!
-Barry
signature.asc
Description: PGP signature
process.
I agree that it's not ideal, but for certain packages that are also
distributed separately, it can be much easier to keep the tests with the code,
and I'm inclined to defer to the primary maintainer's preference.
-Barry
sig
officially deprecate the
'module' form so that they can be removed in a future version.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscrib
On Feb 16, 2011, at 12:34 PM, Terry Reedy wrote:
>I would like the next release called 3.2.0 rather than just 3.2.
+1
(I'd have said +0 for the humor of it :).
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Py
could release Python 0.9 in time. Guido
>then kept the machine ever since.
Keanu Reeves should definitely play Guido. I guess that means Alex Winter
gets to play Georg.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Py
hope that Python 3 is now stable enough to support migration of major
>projects like Django, Twisted or Zope. Other important projets like
>Distribute, Jinja2, PyQt, PyGObject, pygame, NumPy+SciPy and Sphinx are
>already compatible with Python 3.
Agreed! I hope porting to Python 3 can be
' branch.
I'm sure I'm not the only one who works this way with Subversion. IWBN to
cover this in the devguide (or is it there and I missed it?).
Cheers,
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@p
te thing that I'm missing from Bazaar is that 'bzr commit' invokes
my editor and always shows me a 'diff -u' in the commit message buffer. This
is incredibly handy because I don't have to remember to do the diff in a
different window, and I always have all
On Feb 25, 2011, at 01:39 PM, Benjamin Peterson wrote:
>Ah, this reminds me. Figuring out what to do with the AST version
>should probably be a hg roadmap topic.
Is there a bug tracker for the conversion?
-Barry
signature.asc
Description: PGP sig
e a file which lines to commit or
>not. A bit risky but very handy when you have a few oneliners to commit
>or not to commit.
You mean, TortoiseHg supports incremental commits on a single file? That's
kind of neat, but scary. ;)
-Barry
signature.asc
D
On Feb 26, 2011, at 01:49 AM, Éric Araujo wrote:
>Le 25/02/2011 20:43, Barry Warsaw a écrit :
>> On Feb 25, 2011, at 06:40 PM, Adrian Buehlmann wrote:
>> [snip]
>>> Note that each of these branch clones will initially have your local
>>> master repo as the def
nice if I could just delete this message without reading the body.
I guess it's possible for change notifications to encompass multiple named
branches though, right? I'm not sure what to do about that, but it seems like
a less common use case.
-Barry
On Feb 26, 2011, at 07:05 PM
sense, but correct me if I'm wrong, it's the 'merge' operation that
made this happen, right? A merge essentially brings the changesets from one
branch into another.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev ma
essage file. It's still not right though because if the diff
lines aren't prepended with 'HG:', they end up in the commit message. Arg.
Oh well, I can clearly hack a more complicated script together. It's such a
blindingly obvious improvement, it's too bad '
On Feb 26, 2011, at 02:05 PM, R. David Murray wrote:
>On Sat, 26 Feb 2011 13:08:47 -0500, Barry Warsaw wrote:
>> $ cd py27 # now I want to synchronize
>> $ hg pull -u ssh://h...@hg.python.org/cpython
>>
>> but I'm not going to remember that url every time. It wo
;> test-driven-development
>> but need to do some exploration first. You can hack around non-TDD until
>> you're confident of your approach, shelve all your changes, then
>> incrementally
>> apply them back as you write each
;There's an app for that."
:)
-Barry
signature.asc
Description: PGP signature
___
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
#x27;t we?
Do you know how thorough 'bzr check' is? I don't, but then I've never used it
or felt the need to. ;)
>> Oh, and 'bzr info' always tells you what the push and pull locations are.
>
>You can use 'hg paths' for that:
Nice, thanks.
FWIW, this modification to hgeditor does a reasonable approximation of 'bzr
commit' including the diff -u output.
Cheers,
-Barry
#!/bin/sh
#
# This is an example of using HGEDITOR to create of diff to review the
# changes while commiting.
# If you want to pass your favourite editor
tor. The extension had 10 lines of code.
We should find a place (i.e. repository) to stash these useful add-ons and
hacks so that all Python developers can find them.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
On Feb 28, 2011, at 04:15 PM, Antoine Pitrou wrote:
>On Mon, 28 Feb 2011 10:08:26 -0500
>Barry Warsaw wrote:
>>
>> >BTW, I had not heard of hgeditor before, and wrote a small hg extension to
>> >do what you want (with HG: prefix :) before I saw that others had alr
Since there will be no
Python 2.8, our own build system shouldn't ever be changed to add such a link,
but we can recommend it for consistency among distros, which would be free to
adopt it or not.
-Barry
signature.asc
Description: PGP signature
On Mar 02, 2011, at 02:49 PM, James Y Knight wrote:
>On Mar 2, 2011, at 12:14 PM, Barry Warsaw wrote:
>> I don't have a problem with adding such a symlink, and I think it should be
>> done by Informational PEP, not Standards Track PEP. Since there will be no
>> Python
e day.
I also don't think we have to worry about a Python 4. I'm skeptical it will
ever happen, because really, how many big warts in Python 3 do you think we'll
need to break in a backward incompatible way? If it does, and history holds
true, it'll be 15
rpmbuild", rather
>than manually patching hundreds of files.
>
>Note that this would only cover shebang lines at the tops of scripts.
JFDI!
FWIW, a quick grep reveals about two dozen such scripts in /usr/bin on
Ubuntu. We should fix these. ;)
-Barry
signature.asc
Description: PGP sig
H (a shell alias might
>also work). You could configure this with environment-modules[1]_ if Debian
>supports using that in packaging.
I wonder if Debian's alternatives system would be appropriate for this?
http://wiki.debian.org/DebianAltern
Folks, please stop CC'ing p...@python.org for non-PEP submissions. They all
get held for moderator approval. I've approved a few of them, but I'm going
to start rejecting them (so you get a bounce :) unless the message actually
contains a PEP.
cheerfully-co-editing-peps-
d into our workflow, but it's cool enough
that I think we should promote it more. Will that be easier once we're
permanently on Mercurial?
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http:
don't even include actual
scripts in my packages any more, I just add the right goo to setup.py and let
distutils DTRT:
setup(
# ...
entry_points= {
'console_scripts' : list(scripts),
},
# ...
)
-Barry
signature.asc
Description: PGP signatur
On Mar 04, 2011, at 05:35 PM, Michael Foord wrote:
>That (below) is not distutils it is setuptools. distutils just uses
>`scripts=[...]`, which annoyingly *doesn't* work with setuptools.
Sure, but that'll all be moot when distutils2 is integrated into Python
3.3, r
On Mar 03, 2011, at 08:09 PM, Toshio Kuratomi wrote:
>Note to dmalcolm: IIRC, that also means that the Feature page you point to
>isn't going to happen either. Barry -- if other distros adopted stronger
>policies, then that might justify me taking this back to the Packaging
>C
On Mar 05, 2011, at 01:33 AM, Nick Coghlan wrote:
>On Sat, Mar 5, 2011 at 1:10 AM, Barry Warsaw wrote:
>> Folks, please stop CC'ing p...@python.org for non-PEP submissions. They all
>> get held for moderator approval. I've approved a few of them, but I'm going
1601 - 1700 of 2826 matches
Mail list logo
