Jim Jewett schrieb:
It has been quite a while since I worried about my own patches going
stale; I just want to know how my review time can be more useful.
Once a committer has already decided to look at a patch, comments may
make the next step easier.
But is there anyway to flag an issue
Barry Warsaw schrieb:
Jira had a way of automatically assigning certain categories to certain
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
Nilton Volpato wrote:
If you open many member files concurrently how does file cache will
work? Or how many seeks you will have to do if you read from one
member file and from other alternatingly?
If the OS file system cache is doing its job properly,
I don't think the seeking should be a
[EMAIL PROTECTED] schrieb:
More to the point, we know the cost, what's the benefit? Is there any
sort of bug that it is likely to prevent in *new* code?
Yes. People are more likely to classify the file as no extension,
which more likely meets the user's expectation. Also, it won't happen
Terry Jones schrieb:
I do think the behavior can be improved, and that it should be fixed, but
at a place where other incompatible changes will also be being made,
Indeed, 2.6 is such a place. Any feature release can contain
incompatible behavior, and any feature release did contain
Ron Adam schrieb:
But the tracker needs to be able to actually track the status of individual
items for this to work. Currently there's this huge list and you have to
either wade though it to find out the status of each item, or depend on
someone bring it to your attention.
Well, the
Nilton Volpato schrieb:
My Google Summer of Code project was just about this, and I
implemented a lot of nice features. These features include: file-like
access to zip member files (which solves your problem, and also
provides a real file-like interface including .read(), .readline(),
etc);
Giovanni Bajo schrieb:
On 06/03/2007 10.52, Martin v. Löwis wrote:
I can't see that the barrier at contributing is high.
I think this says it all. It now appears obvious to me that people
inside the mafia don't even realize there is one. Thus, it looks like
we are all wasting time in
As an outsider who has submitted a handful of patches and has always
wanted to become more involved.. I would like to comment as I feel like
I am the target audience in question. I apologize ahead of time if I am
speaking out of place.
Martin v. Löwis wrote:
Phil Thompson schrieb:
1. Don't
Martin v. Löwis wrote:
Paul Moore schrieb:
Here's a random offer - let me know the patch number for your patch,
and I'll review it.
Surprisingly (and I hope Scott can clarify that), I can't find anything.
Assuming Scott's SF account is geekmug, I don't see any open patches
(1574068 was
Han-Wen Nienhuys schrieb:
1608267 - added comment, asking for explanation. looks bogus.
1608579 - problem analysis + solution looks good
1507247 - I can reproduce the problem it tries to fix. Fix looks ok.
1520879 - trivial fix; should go in. disregard the comment about relative
--prefix
On 3/7/07, Martin v. Löwis [EMAIL PROTECTED] wrote:
Terry Jones schrieb:
I do think the behavior can be improved, and that it should be fixed, but
at a place where other incompatible changes will also be being made,
Indeed, 2.6 is such a place. Any feature release can contain
incompatible
Martin v. Löwis wrote:
Ah, I had missed the point that it's just binary formatting that
you are concerned with (and then I missed that binary is base 2,
rather than sequence of bits)
Apologies for not being clear. It's easy to forget that others don't
share the context of something you've
A.M. Kuchling wrote:
FWIW, I have a related perception that we aren't getting new core
developers. These two problems are probably related: people don't get
patches processed and don't become core developers, and we don't have
enough core developers to process patches in a timely way. And so
Martin v. Löwis wrote:
I never considered it an extension. Ask 10 people around you to see
what a leading dot on Unix in a file name means, and I would be
suprised if more than one answered it separates the file name from
the extension. Most of them likely include hidden file in their
On 06/03/07, Scott Dial [EMAIL PROTECTED] wrote:
Martin v. Löwis wrote:
Paul Moore schrieb:
Here's a random offer - let me know the patch number for your patch,
and I'll review it.
Surprisingly (and I hope Scott can clarify that), I can't find anything.
Assuming Scott's SF account is
Martin v. Löwis wrote:
Terry Jones schrieb:
I do think the behavior can be improved, and that it should be fixed, but
at a place where other incompatible changes will also be being made,
Indeed, 2.6 is such a place. Any feature release can contain
incompatible behavior, and any
Michael Foord schrieb:
This raises a point which is related to the 'encouraging developers' thread.
I created this patch as part of a Python bug day over a year ago. The
bug day was trumpeted as being a good place for 'newbies' who wanted to
contribute to Python could start, and implied
Martin v. Löwis [EMAIL PROTECTED] wrote:
Phillip J. Eby schrieb:
I consider it correct, or at the least, don't think it should be
changed, as it would make the behavior more difficult to reason about
and introduce yet another thing to worry about when writing
cross-version code.
On 07/03/07, Georg Brandl [EMAIL PROTECTED] wrote:
If it was the last bug day you speak about, this was a bit unfortunate since
it
was only me and Tim who were present for a longer time, and not busy with some
server maintenance tasks. I guess I just picked the wrong day ;)
Agreed - the
Facundo Batista schrieb:
How many people want to submit a patch, or even a bug, or finds a patch
to review, but don't know how to do something and thinks that python-dev
is not the place to ask (too high minds and experienced people and
everything)?
What I propose is a dedicated place
Paul Moore schrieb:
On 07/03/07, Georg Brandl [EMAIL PROTECTED] wrote:
If it was the last bug day you speak about, this was a bit unfortunate since
it
was only me and Tim who were present for a longer time, and not busy with
some
server maintenance tasks. I guess I just picked the wrong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 6, 2007, at 10:16 PM, [EMAIL PROTECTED] wrote:
Does the proposed renaming include any restructuring (e.g. making
hierarchies out of all or part of the stdlib where none existed
before)? It
wasn't obvious to me. For example, might there
Why not offer a Python patching tutorial at the next US/Euro PyCon? It
seems like there's plenty that could be taught. I'd attend. I'd suggest
that that specific tutorial be offered free, or be paid for by sponsors.
Similarly, the first day of the post-PyCon sprints could have a group
learning
Paul Moore schrieb:
1. Open a new patch, with your recommended changes.
I'd like to second this. If you are creating a patch by responding in a
comment, it likely gets ignored.
2. Address the comments made against Tony's patch, in yours.
3. Add a recommendation to Tony's patch that it be
On 3/6/07, Guido van Rossum [EMAIL PROTECTED] wrote:
On 3/6/07, Adam Olsen [EMAIL PROTECTED] wrote:
I think calling it timeout in the API is fine. The documentation
can then clarify that it's an idle timeout, except it only applies
when blocked in a network operation.
Since idel timeout
Guido Since idel timeout is not a commonly understood term it would
Guido be even better if it was explained without using it.
I think it's commonly understood, but it doesn't mean what the socket
timeout is used for. It's how long a connection can be idle (the client
doesn't
[Scott Dial]
While I understand that this tit-for-tat mechanism is meant to ensure
participation, I believe in reality it doesn't, as the 400-some
outstanding patches you referenced elswhere indicate.
. . .
If nothing else, as an outsider there is no way to know why your patch
gets ignored
On Wed, Mar 07, 2007 at 04:32:27PM +0100, Georg Brandl wrote:
If it was the last bug day you speak about, this was a bit unfortunate
since it
was only me and Tim who were present for a longer time, and not busy with
some
server maintenance tasks. I guess I just picked the wrong day ;)
Bug
Martin v. Löwis wrote:
Ron Adam schrieb:
But the tracker needs to be able to actually track the status of
individual items for this to work. Currently there's this huge list
and you have to either wade though it to find out the status of each
item, or depend on someone bring it to your
Martin v. Löwis [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
| [EMAIL PROTECTED] schrieb:
| Maybe you aren't grounded so much in Unix history. It really feels
| wrong that a dotfile is considered as having an extension.
I have not been on *nix for nearly 20 years and I agree that
Martin v. Löwis [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
You may ask yourself why this specific patch was unreviewed for
so long. My own explanation is that it is a highly complicated
algorithm (as any kind of cryptographical algorithm), so nobody
felt qualified to review it.
Hi,
Could I be granted rights to the SF tracker? I'm going through and
reviewing some older patches, and I'd like to be able to close
invalid/rejected patches (eg, 1492509) and upload changed patches.
My SF username is collinwinter.
Thanks,
Collin Winter
Giovanni Bajo [EMAIL PROTECTED] wrote:
On 3/6/2007 3:11 AM, Josiah Carlson wrote:
Giovanni Bajo [EMAIL PROTECTED] wrote:
I think this should be pushed to its extreme consequences for the standard
library. Patching the standard library requires *much less* knowledge than
patching the
[Collin Winter]
Could I be granted rights to the SF tracker?
Done.
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On 3/6/07, Barry Warsaw [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Supported Renamings
===
There are at least 4 use cases explicitly supported by this PEP:
- - Simple top-level package name renamings, such as ``StringIO`` to
Bill Janssen wrote:
If you really need a name other than timeout (which seems fine to
me), how about waiting-with-mild-trepidation-timeout?
Something like response timeout might be more descriptive.
--
Greg
___
Python-Dev mailing list
When Python's import machinery is initialized, the oldlib package is
imported. Inside oldlib there is a class called ``OldStdlibLoader``.
This class implements the PEP 302 interface and is automatically
instantiated, with zero arguments. The constructor reads all the
``.mv`` files from the
On Wed, Mar 07, 2007 at 11:10:22AM +0100, Martin v. L?wis wrote:
- Giovanni Bajo schrieb:
- On 06/03/2007 10.52, Martin v. L?wis wrote:
-
- I can't see that the barrier at contributing is high.
-
- I think this says it all. It now appears obvious to me that people
- inside the mafia
Martin v. Löwis wrote:
David Abrahams schrieb:
I tried building with MS Visual Studio 2005 from PCBuild8/pcbuild.sln,
and for me it fails miserably. The first major complaint comes when
linking pythoncore, where the _init_types symbol can't be found. On
the other hand, allowing MSVS to
Greg Ewing wrote:
Michael Foord wrote:
With the
proposed changes, modules that do this would *continue* to work, surely
?
Probably, but it might mean they were no longer thread
safe. An exception caught and raised in one thread would
be vulnerable to having its traceback
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Re: the discussion in:
http://mail.python.org/pipermail/python-dev/2006-March/062823.html
Just as an FYI, the tlslite package (http://trevp.net/tlslite/) got
broken in Python 2.5 and needed the exact fix quoted in the URL above.
It was an easy fix,
Hi python-dev,
MvL wrote:
the on-disk repository is mighty big and it doesn't work very well
on non-Linux systems (at least, not last I looked.)
Yes, mercurial or Bazaar do its job better on Windows etc. (and are
written in Python :-)
Not true. The on-disk repository is now one of the more
Google's Summer of Code is on again!
I'm in the process of submitting the application for PSF to again be
a mentoring organization.
A mailing list has been set up for people who are interested in
mentoring for the PSF. If you aren't able or willing to mentor but
still want to participate
Hi,
Jason Orendorff wrote:
While we're at it, patch 1669539 makes a similar incompatible change
to ntpath.isabs().
The patch is incomplete (no docs)
After reading your mail, I've just posted a new version of the patch which adds
documentation.
but ripe for a note of encouragement (or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 4:36 PM, Brett Cannon wrote:
Third party package renaming is also supported, via several public
interfaces accessible by any Python module.
I guess a .pth file could install the mappings for the third-party
modules.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 5:46 PM, BJörn Lindqvist wrote:
When Python's import machinery is initialized, the oldlib package is
imported. Inside oldlib there is a class called ``OldStdlibLoader``.
This class implements the PEP 302 interface and is
On 3/7/07, Titus Brown [EMAIL PROTECTED] wrote:
On Wed, Mar 07, 2007 at 11:10:22AM +0100, Martin v. L?wis wrote:
- Giovanni Bajo schrieb:
- On 06/03/2007 10.52, Martin v. L?wis wrote:
-
- I can't see that the barrier at contributing is high.
-
- I think this says it all. It now appears
Josiah Carlson schrieb:
Now it's becoming difficult: several people in favor, some opposed...
What about changing the semantics of splitext and creating a new
function (available on all platforms) that does what the Windows version
currently does?
For people who want the one semantic on
On 3/7/07, Barry Warsaw [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 4:36 PM, Brett Cannon wrote:
Third party package renaming is also supported, via several public
interfaces accessible by any Python module.
I guess a .pth file
Titus Brown schrieb:
Hi, I just wanted to interject -- when I used the word mafia, I meant
it in this sense:
Informal. A tightly knit group of trusted associates, as of a political
leader: [He] is one of the personal mafia that [the chancellor]
brought with him to Bonn.
(Martin, I
Facundo Batista schrieb:
I finally understood the problem, and build python from the repository,
and made the tests from *this* python (actually, this was an easy step
because I'm on Ubuntu, but *I* would be dead if working in Windows, for
example).
Ok. *Me*, that I'm not ashame of asking
Georg Brandl schrieb:
Of course, the channel would have to be made an official Python development
tool and advertised on e.g. the website. Also, it couldn't hurt if some of the
other devs would frequent it too, then :)
I definitely won't: I don't use IRC (or any other chat infrastructure),
[Collin Winter]
I don't suppose you've changed your mind about removing operator.truth
and operator.abs in the seven months since this discussion?
[GvR]
No, though I think that operator.truth should be renamed to operator.bool.
I like the idea that for each built-in op there's a callable in
They do, by emphasizing the relationship with special methods.
On 3/7/07, Raymond Hettinger [EMAIL PROTECTED] wrote:
[Collin Winter]
I don't suppose you've changed your mind about removing operator.truth
and operator.abs in the seven months since this discussion?
[GvR]
No, though I think
[Facundo]
Me, for example, has an actual question to this list: How can I know,
if I change something in the doc's .tex files, that I'm not broking
the TeX document structure?.
[MvL]
You don't have to know. As a general contributor, just submit your
patch, and perhaps the reviewer will catch
On 3/7/07, Martin v. Löwis [EMAIL PROTECTED] wrote:
Me, for example, has an actual question to this list: How can I know,
if I change something in the doc's .tex files, that I'm not broking
the TeX document structure?.
You don't have to know. As a general contributor, just submit your
On 3/7/07, Raymond Hettinger [EMAIL PROTECTED] wrote:
We should try to keep the documentation buildable at all times so that it
will remain visible to everyone at http://docs.python.org/dev/ .
Broken doc doesn't get pushed though. So the worst that will happen
is that the dev doc will be
On 3/7/07, James Tauber [EMAIL PROTECTED] wrote:
Google's Summer of Code is on again!
I'm in the process of submitting the application for PSF to again be
a mentoring organization.
Because I would like core Python projects to be well represented, I
particularly encourage python-devers to
While I guess there's nothing to stop Jython applying in its own
right, it makes far more sense to be under the umbrella of PSF. PyPy
projects last year were under PSF, for example.
I would *strongly* encourage the submission of some Jython projects
under the PSF umbrella.
James
On
On 3/7/07, James Tauber [EMAIL PROTECTED] wrote:
I would *strongly* encourage the submission of some Jython projects
under the PSF umbrella.
Great! I'll do my best to get some submitted.
-Frank
___
Python-Dev mailing list
Python-Dev@python.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 7:39 PM, Brett Cannon wrote:
I think it's important to import on demand only though.
And I agree.
Cool.
I should
probably make that clear in the PEP wink. IOW, import email
should not by side-effect import all sub-modules
On 3/7/07, Barry Warsaw [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 7, 2007, at 7:39 PM, Brett Cannon wrote:
I think it's important to import on demand only though.
And I agree.
Cool.
I should
probably make that clear in the PEP wink. IOW,
Hi Martin,
Martin v. Löwis wrote:
[EMAIL PROTECTED] schrieb:
[...]
The use-cases being discussed here would be better served by having new
APIs that do particular things and don't change existing semantics,
though. For example, a guess_mime_type(path) function which could
examine a
Sorry for the delay. We really wanted to put out a 2.5.1 release
earlier. Due to busy and conflicting schedules, we had to postpone a
bit. We are on track for the following schedule:
2.5.1c1 - Tuesday, April 3
2.5.1 -Thursday April 12 (assuming a c2 is not necessary)
I don't know of
Andrew Bennetts [EMAIL PROTECTED] wrote:
Glyph's proposing that rather than risk breaking existing code (and in the
worst
possible way: silently, giving wrong answers rather than exceptions), we
examine
what benefits changing splitext would bring, and see if there's a way to get
those
On 3/7/07, Raymond Hettinger [EMAIL PROTECTED] wrote:
[Collin Winter]
I don't suppose you've changed your mind about removing operator.truth
and operator.abs in the seven months since this discussion?
[GvR]
No, though I think that operator.truth should be renamed to operator.bool.
I
Josiah Carlson wrote:
[...]
Offer a new splitext that uses X on posix and Y on win32, but causes a
DeprecationWarning with pointers to the two renamed functions that are
available on both platforms.
For people who want the old platform-specific functionality in previous
and subsequent
Andrew Bennetts [EMAIL PROTECTED] wrote:
Josiah Carlson wrote:
[...]
Offer a new splitext that uses X on posix and Y on win32, but causes a
DeprecationWarning with pointers to the two renamed functions that are
available on both platforms.
For people who want the old
69 matches
Mail list logo
