> I am trying to figure out how to self sign a py2exe winxp executable
> with signtool. Anyone know?
Dear William,
This list (python-dev) is for the development of Python, not the
development with Python. I recommend to use either python-list, or
the py2exe-users list for this question.
Regard
Nice!
Python 2.7 is waiting, let's get started! :)
Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On Thu, Oct 2, 2008 at 11:59 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Congratulations, Barry!!!
>
> On Wed, Oct 1, 2008 at 8:46 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On behalf of the Python development team and the Python comm
On Thu, 2 Oct 2008 01:46:45 pm Barry Warsaw wrote:
> On behalf of the Python development team and the Python community, I
> am happy to announce the release of Python 2.6 final. This is the
> production-ready version of the latest in the Python 2 series.
I'd like to thank you all very much for yo
Congratulations, Barry!!!
On Wed, Oct 1, 2008 at 8:46 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On behalf of the Python development team and the Python community, I am
> happy to announce the release of Python 2.6 final. This is the
> produc
Huzzah!
--
Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/
"...if I were on life-support, I'd rather have it run by a Gameboy than a
Windows box." --Cliff Wells, comp.lang.python, 3/13/2002
___
Python-Dev mailing list
Python-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 2.6 final. This is the
production-ready version of the latest in the Python 2 series.
There are many new features and modules, impro
Hi All,
I am trying to figure out how to self sign a py2exe winxp executable with
signtool. Anyone know? I saw this which looked kind of promising:
http://markmail.org/message/zj5nzechzgmjuu7c#query:signtool%20python+page:1+mid:s4jrb2hter4zxvg3+state:results
-Tim
P.S.
Python rocks!
__
Bill Janssen wrote:
> Perhaps PEP 355 just went too far.
That was certainly one of the major objections to it. A filesystem path
object which didn't try to combine a half-dozen different modules into
methods on a single object, but instead focused on solving a few
specific problems with using raw
>> SQLite has a similar problem with NULLs, and I'm definitely sticking
>> paths in there, too.
>
> I think that you can say "all C libraries".
Just for the sake of nit-picking: the socket library, and the regular
POSIX stream IO library (as well as C standard "unformatted" IO) deal
just fine wit
[EMAIL PROTECTED] wrote:
> > I'm actually sort of liking this idea. A Pathname class, for
> > convenience
> > a subtype of String, but containing the underlying binary
> > representation
> >used by the OS. Even non-unicode pathnames could be represented.
>
> On the one hand, I agree with you -
On 03:54 pm, [EMAIL PROTECTED] wrote:
I'm actually sort of liking this idea. A Pathname class, for
convenience
a subtype of String, but containing the underlying binary
representation
used by the OS. Even non-unicode pathnames could be represented.
On the one hand, I agree with you - excep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 30, 2008, at 7:27 AM, Jan Mate(jek <[EMAIL PROTECTED]> Mate> wrote:
Thanks for your answer. I guess the process is the real problem then.
- From what i could observe, the connection between vendor-sec and
PSRT is
not really working as it
M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> On 2008-10-01 09:54, Ulrich Eckhardt wrote:
> > On Tuesday 30 September 2008, M.-A. Lemburg wrote:
> >> On 2008-09-30 08:00, Martin v. Löwis wrote:
> Change the default file system encoding to store bytes in Unicode is
> like introducing a new Py
techtonik wrote:
Can somebody remind how to check script compatibility with old Python versions?
I can remember PHP_CompatInfo class for PHP that parses a script or directory to
find out the minimum version and extensions required for them to run,
and I wonder
if there was anything like this for
On Wed, Oct 1, 2008 at 1:05 AM, Simon Cross
<[EMAIL PROTECTED]> wrote:
> On Wed, Oct 1, 2008 at 12:04 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>> Plus, even on Linux Unicode is *usually* what you should be doing,
>> unless you're writing a backup tool.
>
> I still find this line of reasoning
Simon Cross writes:
> a) There is some chance that at least ASCII characters will be
> displayed correctly if getfilesystemencoding() is similar to the
> encoding used and corrupted filenames will display correctly except
> for corrupted characters.
All you're saying is that the cases *you* c
Can somebody remind how to check script compatibility with old Python versions?
I can remember PHP_CompatInfo class for PHP that parses a script or directory to
find out the minimum version and extensions required for them to run,
and I wonder
if there was anything like this for Python?
--
--ana
[EMAIL PROTECTED] wrote:
> The reasoning is that a lot of software doesn't care if it's wrong for
> edge cases, it's really hard to come up with something that's correct
> with respect to all of those edge cases (absurdly difficult, if you need
> to stay in the straightjacket of string / bytes type
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been out of town since Friday, but I don't yet see anything in
the 700 billion email messages I'm now catching up on that leads me to
think we need to delay the release. Yay!
I will be on irc later today and will be trolling through the tr
On Wed, Oct 1, 2008 at 12:25 PM, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> Simon Cross writes:
>
> > I still find this line of reasoning a bit worrying. Imagine an end
> > user application like a music player. The user discovers that he can't
> > see some .mp3 or .ogg file from the music
Simon Cross writes:
> I still find this line of reasoning a bit worrying. Imagine an end
> user application like a music player. The user discovers that he can't
> see some .mp3 or .ogg file from the music player that is visibile is
> the file manager. I would expect him to file a bug on the m
On 2008-10-01 09:54, Ulrich Eckhardt wrote:
> On Tuesday 30 September 2008, M.-A. Lemburg wrote:
>> On 2008-09-30 08:00, Martin v. Löwis wrote:
Change the default file system encoding to store bytes in Unicode is
like introducing a new Python type: .
>>> Exactly. Seems like the best solut
Le Wednesday 01 October 2008 04:06:25 [EMAIL PROTECTED], vous avez écrit :
> b = gtk.Button(u"\u/hello/world")
>
> which emits this message:
> TypeError: OGtkButton.__init__() argument 1 must be string without
> null bytes or None, not unicode
>
> SQLite has a similar problem with NULLs
On Wed, Oct 1, 2008 at 12:04 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Plus, even on Linux Unicode is *usually* what you should be doing,
> unless you're writing a backup tool.
I still find this line of reasoning a bit worrying. Imagine an end
user application like a music player. The user
On Tuesday 30 September 2008, M.-A. Lemburg wrote:
> On 2008-09-30 08:00, Martin v. Löwis wrote:
> >> Change the default file system encoding to store bytes in Unicode is
> >> like introducing a new Python type: .
> >
> > Exactly. Seems like the best solution to me, despite your polemics.
>
> Not a
On Wed, Oct 1, 2008 at 12:05 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Actually on Windows the syscalls use the encoding that Microsoft uses
> -- when using bytes we use the Windows bytes API and when using str we
> use the Windows wide API. That's the most platform-compatible
> approach.
27 matches
Mail list logo
