that pertain to
Python-the-language. Remember too that PEPs drive language changes, PEPs
(generally) apply to all implementations of the language, and python-dev is
where PEPs get discussed.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@py
On Jun 03, 2012, at 01:22 PM, Martin v. Löwis wrote:
>- Some people (Barry in particular) are in favor of timed releases.
> I don't know what the actual motivation for timed releases is, but
Timed releases in general can provide much better predictability for others
depending on tho
#x27;final', 0)``.
Fixed.
>> + However, for a structured record type use
>> :func:`~collections.namedtuple`
>>
>
>What's with the ~?
I'm not sure, but it seems to result in a cross-reference, and I see tildes
used elsewhere, so I guess it's some reS
but never
got off my butt to do anything about it. Thanks for filing this Dirkjan.
JFDI-ly y'rs,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mai
On Jun 04, 2012, at 02:18 PM, Dirkjan Ochtman wrote:
>Personally, I would really like not having to think about the time
>module at all, except if I wanted to go low-level (e.g. get a Unix
>timestamp from scratch).
+1
Oh and, practicality beats purity
On Jun 04, 2012, at 11:39 AM, Brett Cannon wrote:
>OK, then I would add a test to make sure this happens, like
>``self.assertEqual(sys.implementation.name, sys.implement.name.lower())``
>if you don't want to bother documenting it to make sure other VMs conform.
Good idea.
e datetimes know that? I would expect that an aware
datetime would have that information but not naive ones.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinf
r to be explicit that PEP 3143 is
>not coming in Python 3.3?
Nope, I think that's fine.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/
n-dev, but it also means we're not flooding python-dev with
>interminable arcane discussions on import system internals.
I personally already ignore much of python-dev and only chime in on subjects I
both care about and delude myself into thinking I have something useful to
contr
ies. This is
where tools like virtualenv and buildout on the lower end and chef/puppet/juju
on the higher end come into play.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
ploy *their* applications on
the OS. There's just no other sane way to do it.
I do think Python could do better, but obviously it's a difficult problem.
I suspect that having venv support out of the box in 3.3 will go a long way to
solving some class of these pro
ry packages which can be directly
installed on an end-user system.
-Barry
___
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
ttest discover` or whether nose or py.test is
required, etc. etc. is no good.
-Barry
___
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
know what to do.
+1 for hexversion for the reasons Martin states.
-Barry
___
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
in C++ environment.
These are defined as functions in C++.
The minimum patch would #ifdef out the offending
lines in byte_methods.h and pyport.h if compiling
for C++.
I'm going to be releasing a PyCXX release to work around
this issue.
Barry
___
On 24 Jun 2012, at 14:29, Martin v. Löwis wrote:
> On 24.06.2012 14:52, Barry Scott wrote:
>> I see that issue 10910 needs a reviewer for a patch.
>>
>> I know the python code and C++ and offer to review
>> any patches to fix this issue.
>
> Is this even
any explicit permission from the 3.3 RM in the tracker issues for
this commit. I don't read Georg's comment in msg163937 as providing that
permission. Please either revert or have Georg approve the patch in the
tracker.
-Barry
___
Python-De
If a fix is too intrusive
> or too hacky, it might be that the bug must stay unfixed, though.
It seems that the only reason for the problem in the header is to detect an
unexpected use of isspace and friends. I cannot see why you could not at a
minimum remove when C++ compiler is used
On Jul 05, 2012, at 04:36 PM, anatoly techtonik wrote:
>It would be much easier to do this in unified interface for threaded
>discussions, but for now there is no capabilities for that neither in Mailman
>nor in GMail.
You might like to read the mailing lists via NNTP on Gmane.
Cheer
n summer schedule, review is fairly urgent.
OTOH, this is just documentation, so if Georg agrees, and the changes look
mostly sane, then I can commit it and we can fix up the nits later. Either
way, I'd like to commit the docs by mid-next week at the latest (so after rc1
unfortunately).
experience moderating
lists, and at least vaguely understand what's on and off topic for
python-checkins.
Cheers,
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/list
to be made some time before next Sunday.
I expect to land the new import documentation (issue 15295) within the next
day or so, after I slog through the remaining comments. I have unpushed local
changes that still need a little polishing, but I don't wan
ort
>+protocol, many path entry finders also support the same,
>+traditional :meth:`find_module()` method that meta path finders support.
>+However path entry finder :meth:`find_module()` methods are never called
>+with a ``path`` argument (they are expected to record the approp
On Aug 20, 2012, at 05:49 AM, nick.coghlan wrote:
> s/path importer/path based finder/ (because the path based finder is not an
> importer and the simpler 'path finder' is too ambiguous)
+1!
-Barry
___
Python-Dev mailing list
Pytho
'append', the type conversion would not be applied (it makes no sense
to do so).
I have attached a diff to issue 15906 that implements these semantics. If you
agree, then I will apply this to all of 3.3, 3.2, and 2.7, which are all
affected by this bug (because the original fix for
.ArgumentParser()
>>> p.add_argument('--test', dest='test', type=str, default=[], action='append')
_AppendAction(option_strings=['--test'], dest='test', nargs=None, const=None,
default=[], type=, choices=None, help=None, metavar=None)
>>
On Sep 11, 2012, at 03:08 PM, Barry Warsaw wrote:
>Are you sure about that?
>
>% ./python
>Python 3.3.0rc2+ (default:6fea947edead, Sep 11 2012, 15:03:16)
Never mind. Georg didn't pull that patch into his release clone.
(Aside: Georg, maybe you could fiddle with the default
or not when the parser is created. Append to
>'default as base or start' should mean not converting.
Does that mean that for fixing the regression, you favor applying the type
conversion only for action='store' or by only applying it when the default is
a string?
It
bably that's the right fix for the regression. I'll try to whip up
a patch.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/opti
ed
>semantics.
Right. This gets to Chris's observation that we're blurring the meaning of
'default'. For action='append' should that be the default value when no
arguments are given, or the starting value for the append operations?
We might need to add a 'st
On Sep 11, 2012, at 10:13 PM, Georg Brandl wrote:
>> Traceback (most recent call last):
>> File "/home/barry/projects/python/3.3.0/Parser/asdl.py", line 309, in visit
>> meth(object, *args)
>> File "./Parser/asdl_c.py", line 1043, in visitSu
e. This seems
to be the easiest way to preserve the current behavior (the fix for issues
#12776 and #11839) and fix issue #15906.
I'll update the issue and apply this change to the three branches. Georg can
ignore the change for 3.3.0.
-Barry
___
P
d fix breaks the test suite (yes I tried it). So
maybe we have to go back and decide whether the original fix for #12776 and
#11839 is correct.
More detail in the tracker issue.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.
nks for adding these - very handy.
Agreed. Perhaps the 2.7 RM would like to add something similar for that
release?
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.pyt
ely agree that just installing the Cheeseshop tz package should *not*
be enough to prefer it over the system tz data.
Cheers,
-Barry
___
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
m sad because I use an OS that has no tz data. I run the update script
once in a while, adding the --enable flag, and my Python is timezonally
happy.
* I'm sad and lazy. Oh well, Python throws an exception when I try to use a
timezone that isn't UTC.
Cheers,
-Barry
On Oct 01, 2012, at 05:15 PM, Lennart Regebro wrote:
>On Mon, Oct 1, 2012 at 5:11 PM, Barry Warsaw wrote:
>
>> I completely agree that just installing the Cheeseshop tz package should
>> *not* be enough to prefer it over the system tz data.
>
>Do you have another pot
On Oct 01, 2012, at 05:29 PM, Lennart Regebro wrote:
>We seem to be on the same page here.
Well, that was easy! Maybe I should be your PEP Czar :)
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.
hy wouldn't the stdlib just ship with that emulator by default then? If your
OS doesn't have a system database, then you `pip install pytz` ftw.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/list
On Oct 03, 2012, at 06:45 AM, Skip Montanaro wrote:
>Is there a rough list of changes for 3.4 written down somewhere
Let the wild rumpus begin!
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/pyt
do all we can to nurture an increasing culture of alpha-testing.
Definitely.
>[1] in case anyone hasn't noticed, we *are* a growing community, regardless
>of where various analytics put us relative to other languages :)
Which is *fantastic*!
Cheers,
-Barry
___
ueError instead.
>PyUnicode_FromFormatV() is used by PyErr_Format(), so PyErr_Format()
>may now fail with a ValueError if the format string is invalid.
This behavior is inherited from PyUnicode_FromFormat() which documents the
current behavior, so you can't change this in backward incompa
On Oct 08, 2012, at 11:23 PM, Victor Stinner wrote:
>2012/10/8 Barry Warsaw :
>>>Does anyone know if there is a good reason why PyUnicode_FromFormatV()
>>>does not fail on invalid format string, but copies the format string
>>>as-if into the result?
>>>
&g
t;> Note: This is an automated response to your message "Python-Dev Digest, Vol
>> 111, Issue 31" sent on 10/15/2012 4:00:04.
>>
>> This is the only notification you will receive while this person is away.
>
>Enjoy your day off, John K Peck
uld be fine to update the default branch (i.e. 3.4), but I'm not sure
what benefit you gain from making this change to stable branches, and you
could potentially cause build problems, which you may not find out about for a
while, e.g. when 2.7.4 is released and all the distros go to update.
other
>should happen.
I no longer have much interest (or frankly, time) to pursue PEP 407. Deferred
seems about right to me.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
ht
he first instance of a header).
Cheers,
-Barry
___
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
least be interesting to try.
-Barry
___
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
*Python 2* runtime, and trying to call
lsb_release (a Python 3 script on Ubuntu 12.10) while $PYTHONHOME is pointing
at the wrong runtime.
I personally think this is a bug in the VMware player installer script.
-Barry
___
Python-Dev mailing list
Python-Dev@p
On Oct 22, 2012, at 04:30 PM, Christian Heimes wrote:
>I think it's a bug in lsb_release, too. It should use the -E option in
>its shebang:
Indeed, thanks! I'd forgotten about -E.
(bug updated btw)
-Barry
signature.asc
Descriptio
folks
advocating for it go ahead with it, I just ask that you do it very carefully,
with an eye toward the casual and newbie reader of our code base.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/py
On Oct 28, 2012, at 09:21 AM, georg.brandl wrote:
> PEP 430 is Final.
>From the PEP:
"The existing /py3k/ subpath would be remapped to the new /3/ subpath."
Does "remapped" mean redirects so as not to break the existing py3k urls? If
so,
eader should be added with a link to the relevant post
in the python-dev mailing list archives.
So yes, python-dev needs to be the place where PEPs are discussed and
accepted.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
dated with the new abbreviation.
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/options/python-d
nevermind. =)
I explicitly popped None from path_importer_cache, to try to force it to
ignore the cache. Maybe it's not totally correct (and in practice probably
doesn't matter), but it WFM.
-Barry
___
Python-Dev mailing list
a programming error, should
>a warning be emitted before continuing?
That's not what happens in Python 3.2. In fact, this bug report was triggered
by someone who was already inserting None to sys.path[0]. It is silently
ignored in Python 3.2, b
it be when I have to step through argument parsing to figure
out what's going wrong?
-Barry
___
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
gt;me).
And to me too.
-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
of the
tracker.
-Barry
___
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
gt;bit more complicated, which is why clear thinking is needed. Simply
>copying fields blindly from other packaging systems just isn't going
>to cut it.
+1
>Now, if the will of the community is to turn PyPI into a distro-style
>repository, that's fine...
Please no! -1
wner is and why I'm using their PPA. Or doing a lot of testing in a chroot
first, and probably pinning the package set to just the one(s) from the PPA I
care about.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.py
y, or slip it
like a lump of coal into the xmas stocking of whoever wants to "maintain" it
for the next 20 years.
But anyway, it's already proven enormously helpful to me, so here it is.
Cheers,
-Barry
P.S. Who wants to abuse Jono and Matthew's copyright again and provide a
g
t for now). Python's
memory consumption is an overheard complaint for folks developing for those
platforms.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.
obably overwhelmed by labor costs of
getting them up and running. I am not offering for *that*. ;)
Cheers,
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-
sing in <= Emacs 22. I'm using Emacs 24.2 almost
everywhere these days.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http:/
a wide paragraphs, committed
and pushed.
Thanks Lennart!
-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/o
e comment
on the default value of is_dst for follow ups.
>* ``AmbiguousTimeError``
>
>* ``NonExistentTimeError``
I'm not positive we need separate exceptions here, but I guess it can't hurt,
and with the base class idea above, we can catch both either explicitly, or by
catching the ba
th? Is there a way to uninstall the PyPI package? Does the API
need to provide a method which tells you where the database it is using by
default lives?
Cheers,
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@
On Dec 11, 2012, at 03:37 PM, Brandon W Maister wrote:
>Barry you want github raw:
>https://raw.github.com/regebro/tz-pep/master/pep-04tz.txt
I found that out. I was mostly just complaining. ;)
-Barry
signature.asc
Description: PGP sig
On Dec 11, 2012, at 03:31 PM, Barry Warsaw wrote:
>I've assigned this PEP 431, reformatted a few extra wide paragraphs, committed
>and pushed.
Unfortunately, it looks like the online PEP updater isn't working.
-Barry
signature.asc
Descriptio
ver. It will also raise a ``NonExistentTimeError``
>if a time is specified during the "missing time" in a change to DST.
I think None should be the default.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
P
en an
>explicit True being passed and relying on the default behaviour).
+1
Cheers,
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
h
nd having a main line of development
does mean you have to be careful about merge directionality, but that's
generally something you ingrain in your workflow once, and then forget about
it. The bottom line is that Bazaar users rarely feel the need to rebase, even
though you can if you want to.
C
On Dec 14, 2012, at 12:01 PM, Christian Heimes wrote:
>* It's the release managers responsibility to make sure, all final
> releases contain the current db. This needs to be added to the
> RM's TODO list.
That would be PEP 101.
-Barry
___
from ValueError. That satisfies those
>(including me!) who think it should be a ValueError, while also making
>the exception more specific so it can be handled apart from other
>possible ValueError causes.
>
>In short: +1 to ‘class UnknownTimeZoneError(ValueError)’.
That wou
of choices listed here:
>
>http://www.omappedia.org/wiki/Main_Page
>
>As long as it can run a recent sshd and zsh, I have no preference.
Well, I'm biased of course, but Ubuntu should be easy to install and should
run just fine AFAIK. I'm running 12.10
hould point
somewhere else (is that address ever used in the good path?). I have no idea
where that address is used.
As for the noise issue, well, I hope such failures shouldn't happen very
often. We can set up an auto-discard, but then I worry that problems will
just go unnoticed for days
On Dec 28, 2012, at 07:02 PM, Lennart Regebro wrote:
>On Thu, Dec 20, 2012 at 5:43 PM, Barry Warsaw wrote:
>
>>
>> That would be `class UnknownTimeZoneError(ValueError, TimeZoneError)`.
>>
>
>As of today, in Pytz, UnknownTimeZoneError in fact subclasses KeyErro
ut in PYTHONPATH only the first element is in sys.path.
In detail here is what I'm using to test this:
$ export
PYTHONHOME=/Users/barry/wc/svn/pysvn/WorkBench/Kit/MacOSX/tmp/pysvn_workbench_svn178-1.6.6-0-x86_64/WorkBench.app/Contents/Resources
$ export
PYTHONPATH=/Users/barry/wc/svn/pysvn/Wor
You did not set PYTHONHOME that effects the code in calculate_path a lot.
Also there is platform specific code in tht code.
Barry
On 28 Dec 2012, at 22:30, Antoine Pitrou wrote:
> On Fri, 28 Dec 2012 21:39:56 +
> Barry Scott wrote:
>> I'm trying to track down why bundle
xpect this functionality to be maintained outside of the core
python code?
Barry
On 28 Dec 2012, at 23:57, Ned Deily wrote:
> In article <9e6e3321-b0e7-4e77-afcb-9c7855649...@barrys-emacs.org>,
> Barry Scott wrote:
>> You did not set PYTHONHOME that effects the code in calculate_
be converted to C!).
+1
Or put it another way: Python isn't POSIX but it exposes POSIX APIs, they
should act like POSIX APIs. It's perfectly fine to provide alternative APIs
that have different behavior.
I think it's exactly analogous to Python exposing Windows or
On Feb 03, 2013, at 04:04 PM, Nick Coghlan wrote:
>- someone else volunteers to be BDFL-Delegate for PEP 426 (MvL, perhaps?)
On principle, I think it's a good idea to try to recruit another PEP czar.
I'm not volunteering though, due to lack of time.
C
ries, and has a much longer lifespan than normal releases. I'm pretty sure
we agreed that there would be some exceptions for issues like new platforms
for 2.7.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/
= from_name:
continue
raise
I won't commit this, but it really needs another hasattr() check to be
completely valid.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.
the case with the import system! .
-Barry
___
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
te, so it's
much clearer IMHO.
Works in Python 2, too, fsvo.
-Barry
___
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
s a HOWTO in the documentation.
Cheers,
-Barry
___
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
like a
functional regression. Please file a bug, although it will have to be a new
feature for Python 3.4.
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.pyth
just in Python. OTOH, relying on
__del__ to clean up your tmp files seems rather dubious (well, frankly, so
does most uses of __del__).
Cheers,
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
ing. Probably nobody reads PEP 4 when they get a
DeprecationWarning, but everyone reads the message that's printed, so if
it said something like "This module is deprecated and slated for removal
in Python 2.6", I think we'd be providing better information to
elp get it back to the point where
> you can hold it in your head all at once and still be able to think
> about the problem domain. Keeping cruft impedes that goal.
Agreed, but I think it's mostly going to be an organic process over
time.
-Barry
signature.asc
Description:
e it?
There's really no such thing as "dropping" a PEP, but in any event, we
should still keep PEP 4 to document the procedure for deprecating
modules. It just doesn't need to list any modules (i.e. remove the
sections labeled Obsolete modules, Deprecated modules, and Undeprecated
in peace.
Old documentation lives on in http://www.python.org/doc/versions.html
which seems sufficient for looking up deprecated modules.
-Barry
signature.asc
Description: This is a digitally signed message part
___
Python-Dev mailing list
[EMAIL
ion messages in them often
> fail to identify the Python version in which removal will occur.
> For modules that have been deprecated since 2.1, I would suggest
> to remove them for 2.5, with the option of bringing them back
> in 2.5.1 if people complain
+1 here too.
-Barry
signa
> be phased out. I don't think it is good to leave active modules as
> orphans.
I would like to add deprecation warnings to some of the old
email-related modules for Python 2.5, but I doubt we can remove any of
them until Python 3.0 (or 2014, whichever comes first ).
-Barry
signat
this and I chose cx_Freeze, primarily because it supported
the platforms I needed. It's a very good tool.
I've had some conversations with Anthony Tuininga on the cx_Freeze
mailing list and there seems to be some interest in perhaps putting
together a SIG or something.
-Barry
signat
if we write it in Java. Can I even /find/
25 Python programmers?"
-Barry
signature.asc
Description: This is a digitally signed message part
___
Python-Dev mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscr
ently able to add host names.
-Barry
signature.asc
Description: This is a digitally signed message part
___
Python-Dev mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/p
On Mon, 2004-12-20 at 12:48, Raymond Hettinger wrote:
> Perhaps a rather quick Py2.4.1 would be in order.
+1
-Barry
signature.asc
Description: This is a digitally signed message part
___
Python-Dev mailing list
[EMAIL PROTECTED]
h
2401 - 2500 of 2826 matches
Mail list logo
