Hi,
The register and upload commands have a --repository option that
allows to use them with any server. You can register and upload a
package to any server that has the right set of web services. They
also work with a configuration file called .pypirc
Unfortunately there is no inline optio
Martin v. Löwis v.loewis.de> writes:
>
> Are you (or are you not) aware that this strategy allows for malicious
> code to provide you with a fake JPEG file? If so, does it not concern
> you?
Yes, I'm aware of it and no, it doesn't concern me. When you write a processing
script for internal use t
Tristan Seligmann wrote:
> The correct way to do this is to create a temporary directory, and then
> generate a filename underneath that directory to use.
There is a platform difference here. On unix mktemp will usually provide a
file name in a world-writeable directory (/tmp/) which is wide open
Why does sock.close() not actually close sock?
If I run the code
import socket
sock = socket.socket()
...
sock.close()
I would expect that a system call is done to actually close the socket
and free the file descriptor. But that does not happen. Look at the
code in socket.py. It merely rep
Hello,
2008/5/7 Sjoerd Mullender <[EMAIL PROTECTED]>:
> Why does sock.close() not actually close sock?
>
> If I run the code
>
> import socket
> sock = socket.socket()
> ...
> sock.close()
>
> I would expect that a system call is done to actually close the socket and
> free the file descript
Hi,
Jeroen Ruigrok van der Werven in-nomine.org> writes:
> Would people object if such functionality got added to urllib?
I would ;-) There are IRIs, just that nobody wrote a useful module for that.
There are algorithms in the RFC that can convert URIs to IRIs and the other way
round. IMO tha
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Jeroen Ruigrok van der Werven
> Sent: Wednesday, May 07, 2008 05:20
> To: Tom Pinckney
> Cc: python-dev@python.org
> Subject: Re: [Python-Dev] urllib unicode handling
>
I may be missing something, but it seems that RFC 3987 (which is about
IRIs) basically says:
1) IRIs are identical to URIs except they may have unicode characters
in them
2) IRIs must be converted to URIs before being used in HTTP
3) The way to convert IRIs to URIs is to UTF-8 encode the uni
Hi,
I just wanted to point out a few things:
Community 2.5 bots, 6 out of 8 offline, of the remaining two (which are both
red), one is actually using Python 2.6, not Python 2.5:
http://python.org/dev/buildbot/community/2.5/
Community 2.6 bots, 6 out of 8 offline, but at least the remaining tw
On 2008-05-07 13:37, Amaury Forgeot d'Arc wrote:
Hello,
2008/5/7 Sjoerd Mullender <[EMAIL PROTECTED]>:
Why does sock.close() not actually close sock?
If I run the code
import socket
sock = socket.socket()
...
sock.close()
I would expect that a system call is done to actually close the
Jeremy Hylton wrote:
On Fri, May 2, 2008 at 1:38 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
Thomas Lee wrote:
> Martin v. Löwis wrote:
>>> This leaves us with a few options:
>>>
>>
>> 5. Reuse/Abuse Num(object) for arbitrary constants.
>>AFAICT, this should work out of the box.
> On win32 it will usually (but not always) provide a file name in a directory
> writeable only by the current user.
OS X 10.5 also does this.
>>> import tempfile
>>> tempfile.mktemp()
'/var/folders/Ru/RuapMUan2RWWJ++1YwBnRU++0T6/-Tmp-/tmpjjkKha'
>>> os.system("ls -dl /var/folders/Ru/RuapMUan2RWW
Nick Coghlan wrote:
As Thomas mentions in a later message, making it possible to annotate
nodes would permit Functions to be annotated as being a generator at
the AST stage (currently it is left to the bytecode compiler's
symtable generation pass to make that determination).
Although I gues
"Martin v. Löwis" wrote:
> The proper way to implement this would be IRIs (RFC 3987),
> in particular section 3.1. This is not as simple as just
> encoding it as UTF-8, as you might have to apply IDNA to
> the host part.
>
> Code doing so just hasn't been contributed yet.
But if someone wanted to
Sjoerd Mullender wrote:
> On 2008-05-07 13:37, Amaury Forgeot d'Arc wrote:
> > 2008/5/7 Sjoerd Mullender <[EMAIL PROTECTED]>:
> >> I would expect that a system call is done to actually close the
> >> socket and free the file descriptor. But that does not happen.
> >
> > It does close the socket:
>
Maybe I didn't understand the RFC quite right, but it seemed like how
to handle hostnames was left as a choice between IDNA encoding the
hostname or replacing the non-ascii characters with dashes? I guess in
practice IDNA is the right decision.
Another part I wasn't clear on is whether urll
On Wed, May 7, 2008 at 7:37 AM, Sjoerd Mullender <[EMAIL PROTECTED]> wrote:
> On 2008-05-07 13:37, Amaury Forgeot d'Arc wrote:
>
> > Hello,
> >
> > 2008/5/7 Sjoerd Mullender <[EMAIL PROTECTED]>:
> >
> > > Why does sock.close() not actually close sock?
> > >
> > > If I run the code
> > >
> > > imp
On Wed, May 7, 2008 at 11:43 AM, Thomas Lee <[EMAIL PROTECTED]> wrote:
> Nick Coghlan wrote:
>
> >
> > As Thomas mentions in a later message, making it possible to annotate
> nodes would permit Functions to be annotated as being a generator at the AST
> stage (currently it is left to the bytecode c
> I would be okay with changing the requirements in Py3k so that you are
> required to keep the socket object open at least as long as you plan
> on using the derived stream(s), but this will require some careful
> redesign, especially in the light of SSL support. (Read ssl.py and
> _ssl.c to under
See http://bugs.python.org/issue1348.
Bill
___
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 Wed, May 07, 2008 at 10:29:02AM -0700, Bill Janssen wrote:
> This particular nasty pattern is deeply entwined in all the code that
> touches the HTTP library in any way, so it will be a big job to get
> rid of it -- basically re-writing HTTP support and all the services
> which use it. I didn't
2008/5/7, A.M. Kuchling <[EMAIL PROTECTED]>:
> This would be a good chance for Py3K to dump httplib/urllib/urllib2
> and use some more modern library.
Which modern library do you propose?
--
.Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
On Wed, May 07, 2008 at 03:29:33PM -0300, Facundo Batista wrote:
> > This would be a good chance for Py3K to dump httplib/urllib/urllib2
> > and use some more modern library.
>
> Which modern library do you propose?
I have no idea -- presumably we'd need to compare a bunch of them
(curl, libwget
> Maybe I didn't understand the RFC quite right, but it seemed like how to
> handle hostnames was left as a choice between IDNA encoding the hostname
> or replacing the non-ascii characters with dashes? I guess in practice
> IDNA is the right decision.
I haven't fully understood it, either, but I
> If this is indeed the case, it sounds perfectly legal (according to the
> RFC) and perfectly practical (as required by numerous popular websites)
> to have urllib.quote and urllib.quote_plus do an automatic UTF-8
> encoding of unicode strings before percent encoding them.
It's probably legal, bu
> I just made another attempt to use ctypes to wrap a library, and am
> facing the same problem I had the last time: the documentation doesn't
> really work. I'm wondering if we have any projects underway to
> re-write it?
If *we* had one, *we* would know, right ?-)
So, no. The author of ctypes
Just a friendly reminder that this weekend is the Python sprint weekend! Look
forward to seeing everyone on #python-dev irc.freenode.net over the course of
the weekend!
Trent.
On 16 Apr, 18:52, Trent Nelson wrote:
>
>Following on from the success of previous sprint/bugfix weekends
I was assuming urllib.quote/unquote would only be called on text
intended to be used in non-hostname portions of the URIs. I'm not sure
if this is the actual intent of urllib.quote and perhaps the
documentation should be updated to specify what precisely it does and
then peopel can decide w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
Just a reminder that I'm going to be cutting the releases tonight.
Because of work, I didn't make the 6pm EDT goal, and now I have to run
out for a few hours. I will send another message when I'm ready to
start spinning the release, b
Antoine Pitrou wrote:
When you write a processing
script for internal use there's no reason to worry about security issues like
that
Even without security issues, there's still the potential
for two processes creating temp files at the same time to
trip over each other.
--
Greg
___
Hi,
I have been accepted as a student for GSoC and I'm already working in
my project, "Bringing Ttk to Tkinter". This is my second GSoC, first
time in PSF, and it has been awesome to have Fredrik Lundh as mentor,
we have talked a lot and he is a very nice person.
Regarding the project, I expect i
Barry Warsaw schrieb:
> Hi all,
>
> Just a reminder that I'm going to be cutting the releases tonight.
> Because of work, I didn't make the 6pm EDT goal, and now I have to run
> out for a few hours. I will send another message when I'm ready to
> start spinning the release, but figure it will be
Bill Janssen wrote:
The HTTP client-side library calls "makefile" on the socket, then
closes it, then passes the file returned from "makefile" on to
application code to work with.
Seems to me we really need two different APIs for
doing a makefile()-like operation, depending on
whether you're e
Christian Heimes wrote:
Can you come up with a path that fits the purpose of a base directory?
"~/Library/Application Support/Python" would seem to be
appropriate.
--
Greg
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mail
Christian Heimes wrote:
Can you come up with a path that fits the purpose of a base directory?
Second thoughts, I think there's something better -- there's
already a system-supplied directory on my system called
/Library/Python/2.3 with a site-packages containing a
README that says it's for in
On Tue, May 6, 2008 at 6:52 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> alexandre.vassalotti schrieb:
>
> > Author: alexandre.vassalotti
> > Date: Tue May 6 21:48:38 2008
> > New Revision: 62778
> >
> > Log:
> > Added fast alternate io.BytesIO implementation and its test suite.
> > Rem
Hello.
> The py3k branch has a major show stopper, It's leaking references to the
> max.
Is there any chance this leak also will be fixed?
http://bugs.python.org/issue
Thank you.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.
This has been a fairly interesting discussion about tempfile.mktemp, but can
we return to the original question? Should we begin warning about its use
again? Should we ever warn about it? It appears that NamedTemporaryFile
gives you a reasonable (secure) replacement. I'm happy to document
mktem
Christian Heimes schrieb:
> The py3k branch has a major show stopper, It's leaking references to the
> max.
Fixed ;)
Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 7, 2008, at 9:25 PM, Christian Heimes wrote:
Christian Heimes schrieb:
The py3k branch has a major show stopper, It's leaking references
to the
max.
Fixed ;)
Thanks!
Folks, I apologize. I had some system problems tonight so I fell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 7, 2008, at 9:41 PM, Hirokazu Yamamoto wrote:
Hello.
The py3k branch has a major show stopper, It's leaking references
to the
max.
Is there any chance this leak also will be fixed?
http://bugs.python.org/issue
Not for the alphas,
> Regarding the project, I expect it to be integrated into Python's
> stdlib sometime in the future, I believe it will be in very good shape
> before binaries compiled against tcl/tk 8.5 start showing up.
Actually, I would like to release Python 2.6 and 3.0 on Windows with Tk
8.5 included, prefera
42 matches
Mail list logo
