that points to the new location. What do y'all think about
doing the same for the Python 2.7 and 3.1 branches?
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/l
merge has proven
impossible so far.
I think I'll replace Misc/python-mode.el with Misc/README.Emacs that attempts
to discuss the issue in a neutral way. I'll fix this in Python 2.7, 3.1, and
3.2.
Thanks,
-Barry
signature.asc
Description: PGP signature
___
ould be so compelling about a Python 2.8
that users, package authors, and distros would be willing to undertake this
work?
I'd *much* rather this enthusiasm be spent on making Python 3 rock, and in
porting third party code to Python 3.
-Barry
signature.asc
Description: PGP signature
_
e so, but I think it's actually more fun to be working on something other
people will actually use. ;)
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/py
nger than usual, which we've already done, what
specifically should we do? A no-new-feature Python 2.8 doesn't make sense,
and I'm not convinced that a new-feature Python 2.8 really helps folks who are
stuck on Python 2 for whatever reason.
sphinx/__init__.py", line 44
>except ImportError, err:
> ^
>SyntaxError: invalid syntax
It would be really cool if you fixed this!
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyth
xt file much like Barry is planning to
>do for Emacs and point to the files Antoine is recommending.
The Emacs changes are committed now in py3k, release31-maint, and
release27-maint.
Cheers,
-Barry
signature.asc
Description: PGP signature
___
Pyt
On Oct 27, 2010, at 10:34 AM, R. David Murray wrote:
>To put your mind at ease, Barry, I'd not want to do that either :)
Phew! But I wasn't worried, 'cause I know you're not insane. (Though the
fact that you've effectively inherited the email package does bring tha
to basicConfig()? That would make it pretty easy to get the
formatting style you want without having to explicitly instantiate a
Formatter, at least for simple logging clients.
Cheers,
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mai
ith Michael Foord yesterday and he's writing code
that works in 2.4 through 3.2, so for *some* code bases, it's tricky and ugly,
but possible.
IMHO, those are the kinds of directions we should be thinking about, to help
existing code more easily make the jump to Python
ns would be happy to have a stable
> increasingly de-bugged 2.7 be Python 2 for several years.
>
> --
> Terry Jan Reedy
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> http://mail.python.org/mailman/listinfo/python-
That's a much better idea!
Sent from my digital lollipop.
On Oct 29, 2010, at 3:31 PM, Ian Bicking wrote:
> On Fri, Oct 29, 2010 at 12:21 PM, Barry Warsaw wrote:
> On Oct 29, 2010, at 12:43 PM, Casey Duncan wrote:
>
> >I like Python 3, I am using it for my latest pro
It certainly doesn't have to.
Sent from my digital lollipop.
On Oct 29, 2010, at 4:06 PM, Antoine Pitrou wrote:
> On Fri, 29 Oct 2010 15:54:19 -0400
> Barry Warsaw wrote:
>> Another quick thought. What would people think about regular timed releases
>> if python 2.7?
&
live in the same documentation. By
sectioning the documentation, the module docs can be organized to give both a
user guide with opinionated recommendations, and a complete reference manual.
Cheers,
-Barry
signature.asc
Description: PGP signature
___
didn't adhere to much
regularity. ;/
Cheers,
-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/optio
the code
>>
>
>Please do not make any existing released methods from the unittest module
>non-public or add any deprecation warnings. That will simply cause
>unnecessary code churn and pain for people porting their code from one
>version to the next without benefiting
On Oct 31, 2010, at 04:39 PM, Eric Smith wrote:
>What are your thoughts on adding a str.format_from_mapping (or similar
>name, maybe the suggested "format_map") to 3.2?
+1 for the shorter name.
-Barry
signature.asc
Descriptio
intaining unittest like he has been, plus we could consider using
>>> the new structure so that the public API matches the file structure
>>> when the need arises).
>>
>> Something to note in PEP 8, perhaps?
>
>If everyone agrees with
e in future versions” hold for package
>names?
I would vote "yes". I have seen more and more packages use this convention to
signal that the module name is not intended to be imported directly. This
should be part of any PEP 8 recommendation, IMO.
-Barry
signatu
x27;s their problem (like people depending on bytecode and other
>stuff).
+1
-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.py
l 2012. It's an
ambitious but worthy goal to see if we can transition to Python 3 as the
default Python by then.
-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
ls/world/world us
us originated from United States
I once started to rip it out into a separate package but haven't gotten too
far with that.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://ma
ll, outage should be very short.
>
>Seems to be offline now. I get timeouts.
I just had no problems updating issue 9807.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/l
to commit. With 3.2b1 coming soon, now's the time to do that.
If there are any remaining concerns about the details of the patch, please add
them to the tracker issue. If you have any remaining objections to the
change, please let me know or follow up here.
Cheers,
-Barry
signature.asc
D
it's fine leaving it out of __all__. It's
not a difficult change to work around.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscrib
then the __all__ definition becomes effectively redundant).
Agreed, though I wouldn't *remove* __all__'s, I would establish a convention
where they can be generated programmatically. Keeping __all__ in sync with
the code is a PITA. It screams for automation.
-Barry
signature.asc
;buildbot is highly backwards compatible. As a recommendation, I suggest
>that slaves run at least at the version that is available in Debian
>stable (currently 0.7.8).
Thanks Martin, for all you do to keep our infrastructure humming along
smoothly, including the recent Roundup migration.
-Bar
But only the release
managers should have write access to the svn repositories.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscrib
On Nov 19, 2010, at 06:12 PM, Georg Brandl wrote:
>Am 19.11.2010 15:46, schrieb Barry Warsaw:
>> On Nov 19, 2010, at 11:50 PM, Nick Coghlan wrote:
>>
>>>- date SVN will go read only
>>
>> Please note that svn cannot be made completely read-only. We've
On Nov 10, 2010, at 04:27 PM, Barry Warsaw wrote:
>I finally found a chance to address all the outstanding technical issues
>mentioned in bug 9807:
>
>http://bugs.python.org/issue9807
>
>I've uploaded a new patch which contains the rest of the changes I'm
>pr
On Nov 23, 2010, at 01:50 PM, Michael Foord wrote:
>Right. As it happens I just submitted a patch to Barry Warsaw's enum package
>(nice), flufl.enum [1], to allow namedtuple style creation of named
>constants:
Thanks for the plug (and the nice patch).
FWIW, the documentation for
tion is a
better way to go.
-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;s little reason to change existing working code.
Enums can be used whenever a module or API is updated.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-
t_iter`, i.e. an iterator of integers for
the values in the string. I suspect YAGNI, which is why I didn't just add it,
but I'm not totally opposed to it.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-De
;def __reduce__(self):
>return getattr, (self._class, self._enumname)
>
>in the EnumValue class.
Excellent idea, thanks. Added to flufl.enum in r38. However, only enums
created with the class syntax can be pickled though.
Cheers,
-Barry
signatu
get(name)
> File
> "d:\cygwin\home\db3l\buildarea\3.x.bolen-windows\build\lib\sysconfig.py",
> line 478, in get_config_vars
>_CONFIG_VARS['abiflags'] = sys.abiflags
>AttributeError: 'module' object has no attribute 'abiflags'
As di
On Nov 27, 2010, at 02:01 PM, Michael Foord wrote:
>(Note that there is no *particular* hurry to get this into 3.2 - the beta is
>due imminently. I wouldn't object to it )
Indeed. I don't think the time is right to try to get this into 3.2.
-Barry
signature.asc
Descriptio
t for Python 3, but it should be a new
PEP.
-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/
On Nov 30, 2010, at 12:11 PM, Brett Cannon wrote:
>I will channel Neal: "I decline and/or do not want to respond". =)
PEP 291 updated.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@py
ing language”? like Java?), but I'm pretty sure
>>> I've heard there's a Python 3 compatible version.
>>
>> Uhm... http://pypi.python.org/pypi/Python
>>
>> Anybody wanna remove that, or update it or something? :-)
>
>Entry is for Python 2.5.
>
On Dec 02, 2010, at 08:44 PM, Martin v. Löwis wrote:
>Since the "barry" account already exists, you first need to log into
>that (likely using a password). You can then claim the LP OpenID as
>being associated with that account, and use LP in the future.
Thanks Martin.
-Ba
y code has reached into distutils, but I think you can make
fairly good judgements about whether a change is backward compatible or not.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.
ready.
I do not think it would be a good idea to revert PEP 3149.
-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.or
5 now that we're in beta.
I personal think they're worthwhile changes to go it, but I won't
argue too hard for them since the pydoc fixes can be implemented with
local changes to pydoc.py alone.
Thoughts?
- -Barry
https://sourceforge.net/tracker/?
func=detail&atid=305
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 10, 2006, at 9:52 PM, Barry Warsaw wrote:
> Patch #1520294 adds support for attributes defined with PyGetSetDef
> in extension modules to pydoc, specifically so things like help
> (array.array.typecode) gives something useful,
smells too
much like the True/False thing. However, I believe I can weedle a
fix into pydoc for those types without exposing these new names, so
I'd like to do that if there are no objections.
- -Barry
-BEGIN PGP SIGNATURE-
Versi
in their code we
simply won't know it until after that, no matter how diligent we
are. OTOH, a more formal gamma phase would allow us to say
"absolutely no changes are allowed now unless it's to fix backward
compatibility". No more sneaking in new sys func
e getset and member descriptors. I'm not sure if Georg has had a
chance to look over the latest rev of the patch (which is currently
assigned to him).
I'm basically just looking for an RM pronouncement one way or the
other. Can this be added to 2.5 or does it have to wait for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 13, 2006, at 12:12 PM, Barry Warsaw wrote:
> I've updated SF patch #1520294 and assigned it back to Georg for
> another quick review.
Neal commented in the patch that it might help to explain the
implementation a bit. I&#
y either. You /could/ add
that to Modules/config.c.in but I'm not sure it''s a good idea.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iQCVAwUBRL/rgHEjvBPtnXfVAQLnHwP/Tzy1Iy8nbByuVaYaGrhel9zsdlbRXXlj
8wvLLlmzctmnzBrPBpZKV7aJMdiBd6261SKqPCrDZCj2LEplZ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since Anthony didn't speak up, I took his silence as assent and went
ahead and committed the changes. r50881 and r50885 for *nix and
Windows, just in case the deafening silence turns into a howl of
derision :).
- -Barry
-BEGI
encouraged that the porting effort will be minor (probably no more
than a day's worth of work for both apps combined).
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iQCVAwUBRMoJonEjvBPtnXfVAQJOjAP9HRbakdb39IOtFxGX/wP4QhiXAcNAbXX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Re: Python 2.5 compatibility
On Jul 28, 2006, at 8:57 AM, Barry Warsaw wrote:
> +1. It would give me more type to port and test a few of my
> applications to the new version.
>
> I'm still working on Mailman but the most painful
rg 2 must be a class or type
>>> isinstance(Exception, type(type))
0
Python 2.5b2 (trunk:50835, Jul 25 2006, 23:27:51)
[GCC 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)] on linux2
Type "help", "copyright", "credits" or "license" for more informati
Python 2.5 but also
wanting to avoid perpetuating broken code, this solution seems the
most reasonable.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iQCVAwUBRNNu8HEjvBPtnXfVAQL9MQP/SCuLPFwS0m5vWJ3+i2iVZVCg21eXKQte
R8zoTngSx7unxfn5WQ7Bi8l9Ai1SkmZ7z0mOr6Ubt
ersion) will be the default,
+1. We even have Subversion hooks in our repository to reject any
commits that have tabs in them (except for Makefiles and a few
whitelisted 3rd-party apps that we don't want to reformat).
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin
improving the library and documentation.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBROiAk3EjvBPtnXfVAQKeMQP/QBfHJexDveKoj/nfjRjic3+HBvTupkoA
bga7GmLV7Rn14AoHf+L6n3IhKkE1sIVXwzUmEoOeVN74h3trJSAeEYPjCF7Vt3//
3fZ4SgAlEy3nsOwRYufUtyYU9r36H7Fn7dKTtj+hJCVAzZdA
e, er, under-documented parts of the C API. I do a /ton/ of
embedding/extending work for my Real Job so I think I could justify
some work time devoted to improving things here.
I'll try to take a look at MWH's stuff, but should we go ahead and
check it into Python's svn at som
thinks a 2.3.6 would be useful, but I'm happy to do it if there's community support. I'll also need the usual help with Windows installers and documentation updates.Cheers,-Barry
PGP.sig
Description: This is a digitally signed message part
___
;
> If there will be a 2.3.6, it might be necessary to look at all 2.4
> branch
> fixes and decide which of them are worth backporting.
Right, we'll definitely have to do that, and maybe not much more.
- -Barry
-BEGIN PGP SI
he string that may
> still contain separators.
ISTM this is just begging for newbie (and maybe not-so-newbie)
confusion. Why not just document both as returning (left, sep,
right) which seems the most obvious description of what the methods
return?
- -Barry
-BEGIN PG
suggestive of use cases. IMO, the latter would be better served as
an example in the latex documentation.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRP25cXEjvBPtnXfVAQJ4EwQAuKnVxtyabdtAv/Eu9CcZ8EkcwCJYOoAT
DmgMWeml861Sn4qN6NV1vMKbXljxiKqoSBgbKdpU+FRb6TeNiCis
not ambiguous is it? Seems to work for both partition and rpartition.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRP2+AHEjvBPtnXfVAQLiPAP+N80jHkoT5VNTtX1h2cqD4pONz+j2maCI
QXDBoODucxLDPrig8FJ3c6IcT+Uapifu8Rrvd7Vm8gSPMUsMqAgAqhqNDbXTkHVH
xLk31en2k2fdiCQKQyKJSjE1R1CaFC
believe (left, sep, right) will be the clearest description for all
users, with little chance of confusion.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRP3HIXEjvBPtnXfVAQIx5wP+MPF5tk4moX4jH0yhGvR6gKcGBusyN152
redIr0xiNqECfrIHk
added, the choice of words becomes
> much
> less important.
Ideally too, the terminology (and order) for partition and rpartition
would be the same.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRP3bVXEjvBPtnXfVAQJSKwP9Ev3MPzum3kp4hNDJZyBmEShzPvL2WQv
Hebrew, Arabic, or other RTL language? Do partition and rpartition
suddenly switch directions?
If not, then I think left-sep-right are fine. If so, then yeah, we
probably need something else.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCV
I have the tool chains to build extensions against your binary python
2.2, 2.3 and 2.4 on windows.
What are the tool chain requirements for building extensions against
python 2.5 on windows?
Barry
___
Python-Dev mailing list
Python-Dev@python.org
code. After I perfect my human cloning techniques, I'll be assigning
one of my minions to fix this situation (I'll bet my clean-the-kitty-
litter-and-stalk-er-keep-tabs-on-Britney clone would love to take a
break for a few weeks to work on this).
- -Barry
-BEGIN PGP SIGNATURE---
On Sep 9, 2006, at 2:10 PM, Martin v. Löwis wrote:
> Barry Warsaw schrieb:
>> Thoughts? I don't want to waste my time if nobody thinks a 2.3.6
>> would
>> be useful, but I'm happy to do it if there's community support. I'll
>> also need the usual
n remember attempts to use std::cout would fail and I
think
static object initialisation would fail. The test code would need to
do all these
things and verify they are working.
Barry (PyCXX cxx.sourceforge.net)
___
Python-Dev mailing list
Pyt
I've
read in my career, Python actually ain't too bad. :)
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRRx+AXEjvBPtnXfVAQJgNgP8D9f2ZUqIDTUmQU8BRx4iqjbXQANrdHt1
usZCwguIS4pa0pmUp73E514y+tDs1UzU1E2I2itIifqtKXZuPOSZYG/DWcg4h8vh
KPCygqSDNiW5dr77UP4QBXk3DOoj68
only two objects in the pickle, so I don't have to iterate over it; I
just load the message and then load the dictionary.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRSpyaHEjvBPtnXfVAQLqcgP/VqKqwZfReaQyRGP2DG61978CmbqLOvSY
nsXP/AE88VvO+IHYajfNuJt/okmT
ould have such and such
>> feature, if the corresponding tp_xxx field were set".
>
> I would like to see that cleaned-up for Py3k. Ideally, the NULL or
> non_NULL status of a slot should serve as its flag.
+1 TOOWTDI.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4
patching and re-
releasing their own packages. Since this doesn't affect the
binaries /we/ release, I'm not sure I care enough either.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRS5hD3EjvBPtnXfVAQIlLgP/Rz5ahaeus0VLJT0HmyZUYBf07Crr2e1K
KgCoEDqXZq+L
ce downloads page (if this has
> not been
> done already).
I don't currently have the ability to update the website, but I think
the download page should have a big red star that points to the
security patch. The 2.3.5 page should probably be updated with a
link to the patch too
7;t know what Martin has to do for the Windows build.
Why can't we get buildbot to do most or all of this? At work, we
have buildbot slaves that post installers to a share after successful
checkout, build, and test on all our supported platforms.
- -Barry
-BEGIN PGP SIGNATURE--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 12, 2006, at 5:03 PM, Gregory P. Smith wrote:
> IMHO thats a backwards view; I'm with Barry. Requiring human
> intervention to do anything other than press the big green "go" button
> to launch the "official
nto
doing what is mostly thankless grunt work. ;) OTOH, there's always
new blood with lots of time on there hands coming into the community
looking for a way to distinguish themselves (read: students :).
Maybe someone will step forward and win a little lemony slice of
net.fame.
- -
and the
Cheeseshop are for.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRS7l+XEjvBPtnXfVAQJy6gP/RkGcTXDCBYM/WL/X+sNiTp6ydvFPg20u
SrxUb/vQpNVkjA2GkFJJAXArnsxn8LB2MC+rPDRkkNMYcFw5JAUcf0IR1L+AdFnC
h+68f03XDzbeB8uqVrQ6xObEPXmanvhx1uCrApqFq+zOzqMNlbzUlyGCTLu0Cw
framework
folder to look in allows both to be linked against.
Is there a way to force ld to use a particular version of the python
framework or do
I have to change the symlink each time I build against a different
version?
This type of problem does not happen on Windows or Unix by design.
Barry
and update my build script.
All my code is C++ and in the past distutils lacked C++ support so I
could not use it and have develoer
my own solution to the build problem.
Does distutils work for C++ code these days?
Barry
___
Python-Dev mailing list
Python-De
rsion 92.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 88.1.7)
Any possibility something like that's going on?
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRTwSqHEjvBPtnXfVAQLvwQP/VuTQwwXw
ted back to the last
known good version. At some point I'll try to get us on the latest
release, but I'm a little gunshy about it.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRTw8e3EjvBPtnXfVAQ
ts non-publicness and I don't have a
problem in principle adding such methods. In this particular case,
it seems the patch improves reliability, so +1.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRVNEL3EjvBPtnXfVAQIb0QP+Nmd6XPKQeeXaHrAG/fAFjrVHFn4
d if we were to use it to replace distutils.
There does seem to be overlap between the two tools though, and it
might make for an interesting sprint/project to find and refactor the
commonality.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRVObXHEjvBPtn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 12, 2006, at 3:55 PM, Fredrik Lundh wrote:
> would anyone mind if I added the above classes to the datetime
> module ?
+1. I mean, we have an example of UTC in the docs, so, er, why not
include it in the stdlib?!
- -Barry
tions of any size will have way
more application data than duplicated Python libraries.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRWxVQ3EjvBPtnXfVAQIuMAQAkciyaHCwLnkN+8GwbhUro+vJuna+JObP
AZaNzPKYABITqu5fKPl3aEvQz+9pNUvjM2c/q5p1m/9n34ZBURfgpHa3yk7QcbW0
sud8utdW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 28, 2006, at 2:41 PM, Mike Orr wrote:
> On 11/28/06, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>> For distros like Gentoo or Ubuntu that rely heavily on their
>> own system Python for the OS to work properly, I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 28, 2006, at 4:05 PM, Guido van Rossum wrote:
> On 11/28/06, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>> There's a related issue that may or may not be in scope for this
>> thread. For distros like Gentoo or Ubuntu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 28, 2006, at 4:19 PM, Phillip J. Eby wrote:
> At 01:05 PM 11/28/2006 -0800, Guido van Rossum wrote:
>> On 11/28/06, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>> > There's a related issue that may or may not be in sco
entury! Where was setuptools back in 1996? :)
Seriously though, that does sound cool, and thanks for the tip.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRWzTtXEjvBPtnXfVAQKDwgP+N/nGkHm7e9ZK+DmTEx+gOxPkeQnpKcA2
AHLg9WLJh
ven't really thought this through so maybe it's a stupid idea,
but ISTM that would make management, installation, and use in an
application about as simple as possible. (Oh yeah, add an --
uninstall switch too :).
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
i
I wish I had more time to share ideas about
> packaging, but I know too well that I'm not going to be able to
> back them up with any implementation effort.
Yeah, same here, so I'll shut up now.
> I'd really like Python to use the ~/.local/bin / ~/.local/lib
:) Thanks! I'll read up
on that stuff.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRW5phnEjvBPtnXfVAQKwLgP/doK7aF5zGknK4JCv+rjO4xXKWRwjB0Vk
B08Ee2HlSTcqSe8YIqMOSCRa8LcW86hEFipJmIi8vzcPv0Tr6y+i6yMTq0zhYeyh
lvc7E7wdMY+U78/+ffeDLBNESXkZRzaiv0aH4ZkBf3xOebj58
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 30, 2006, at 9:40 AM, Talin wrote:
> Greg Ewing wrote:
>> Barry Warsaw wrote:
>>> I'm not sure I like ~/.local though - -- it seems counter to the
>>> app-specific dot-file approach old schoolers like me ar
s too. Maybe that means
python -M install --install-dir foo --other-setuptools-options
would work, but I don't think just bare --install does. I'm also not
sure "python -M install" is a big improvement over "egg" or whatever
("
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 30, 2006, at 6:44 PM, Greg Ewing wrote:
> Barry Warsaw wrote:
>
>> When I switched to OS X for most of my desktops, I had several
>> collisions in this namespace.
>
> I think on MacOSX you have to consider that it&#x
to be taken into account:
> - documentation and test cases must be updated to integrate the new
> API
> - for slicing, you need to consider not only omitted indices, but also
> "true" slices (e.g. m[1:5])
> - how should you deal with negative indices?
> - shou
de from __str__ in 2.4.1 and it worked fine). That's the
> oldest version I
> have handy, so I don't know if it was possible in earlier versions.
I don't have anything older than 2.4 laying around either, but IIRC
in 2.3 unicode() di
5.
Ah cool, thanks. I must be misremembering that about some earlier
Python.
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRXbcenEjvBPtnXfVAQIZWAP/aRXJ1Rq0eMVWhYOYvP6Wdy2v5DCj0Arl
yS3n0RURWJj5i+zYtqQUBIJEOcFSLJ69cb1SWl/KTvedI4y0SB
1501 - 1600 of 2826 matches
Mail list logo
