Re: [Python-Dev] PEP 457: Syntax For Positional-Only Parameters

Am 09.10.2013 16:53, schrieb Larry Hastings: > On 10/09/2013 04:26 PM, Georg Brandl wrote: >>> I realize you are -1 on the proposal in general, but I'd be very interested >>> if >>> you could propose an alternate approach where I didn't need "a new sp

Re: [Python-Dev] PEP 457: Syntax For Positional-Only Parameters

Am 09.10.2013 19:00, schrieb Ethan Furman: > On 10/09/2013 09:05 AM, Paul Moore wrote: >> >> I remain -1 on forcing "Python syntax" to support all of these odd corner >> cases (and positional-only is already a corner case, range/addch are >> seriously so). > > Considering the prevalence of positi

Re: [Python-Dev] cpython (3.3): Fix macro expansion of _PyErr_OCCURRED(), and make sure to use it in at least

Am 07.10.2013 20:41, schrieb antoine.pitrou: > http://hg.python.org/cpython/rev/2aee9c41bb79 > changeset: 86140:2aee9c41bb79 > branch: 3.3 > parent: 86136:bd16e333 > user:Antoine Pitrou > date:Mon Oct 07 20:38:51 2013 +0200 > summary: > Fix macro expansion of _PyE

Re: [Python-Dev] cpython: Rename contextlib.ignored() to contextlib.ignore().

Am 11.10.2013 11:43, schrieb Victor Stinner: > [We are discussing issue #15806.] > > 2013/10/11 Antoine Pitrou : >> I don't think that this contextlib.ignore() thing has been discussed a >> lot. > > If we decide to keep the feature, I would prefer a less generic name: > contextlib.ignore_excep()

Re: [Python-Dev] cpython: Rename contextlib.ignored() to contextlib.ignore().

Am 11.10.2013 16:47, schrieb Barry Warsaw: > On Oct 11, 2013, at 09:24 AM, Antoine Pitrou wrote: > >>I don't think that this contextlib.ignore() thing has been discussed a >>lot. >> >>Ezio was -1 on the tracker, and Eric Smith was -0. I'd like to add my >>-1 too. This is a useless addition (the tr

Re: [Python-Dev] cpython: Rename contextlib.ignored() to contextlib.ignore().

Am 11.10.2013 19:24, schrieb Barry Warsaw: > On Oct 11, 2013, at 01:19 PM, Eric V. Smith wrote: > >>But, to continue to paint the shed, shouldn't it be "ignoring", to match >>"closing"? > > Maybe so. Would at least be consistent since both actions (close/ignore) are done at the end of the execut

[Python-Dev] Support for marking limited API elements in C API docs

Hi, in light of the recent thread about PEPs not forming part of the docs, I've just pushed a change that allows to document C API elements not part of the limited API as such. It is done like this: .. c:function:: int _PyTuple_Resize(PyObject **p, Py_ssize_t newsize) :notlimited: I have not

Re: [Python-Dev] Right place for PBKDF2 wrapper

Am 12.10.2013 19:37, schrieb Antoine Pitrou: > On Sat, 12 Oct 2013 19:19:44 +0200 > Christian Heimes wrote: >> Hi, >> >> I have written a interface to OpenSSL's PKCS5_PBKDF2_HMAC() function. It >> implements PKCS#5's password based key derivation function 2 with HMAC >> as pseudo-random function.

Re: [Python-Dev] Support for marking limited API elements in C API docs

Am 12.10.2013 20:20, schrieb Serhiy Storchaka: > 12.10.13 21:04, Georg Brandl написав(ла): >> in light of the recent thread about PEPs not forming part of the docs, >> I've just pushed a change that allows to document C API elements >> not part of the limited API as s

Re: [Python-Dev] Support for marking limited API elements in C API docs

Am 12.10.2013 21:56, schrieb Antoine Pitrou: > On Sat, 12 Oct 2013 21:19:16 +0200 > Georg Brandl wrote: >> Am 12.10.2013 20:20, schrieb Serhiy Storchaka: >> > 12.10.13 21:04, Georg Brandl написав(ла): >> >> in light of the recent thread about PEPs not forming

Re: [Python-Dev] Support for marking limited API elements in C API docs

Am 12.10.2013 22:16, schrieb Antoine Pitrou: >> >> Well, I may be reading PEP 384 wrongly, but the point is exactly to have a >> >> *stable* API for *non-core* developers to rely upon, so that they can >> >> build >> >> extensions that don't need to be recompiled for every version of Python. >> >

Re: [Python-Dev] Support for marking limited API elements in C API docs

Am 12.10.2013 22:09, schrieb Eric V. Smith: > On 10/12/2013 4:04 PM, Georg Brandl wrote: >> Am 12.10.2013 21:56, schrieb Antoine Pitrou: >>> On Sat, 12 Oct 2013 21:19:16 +0200 >>> Georg Brandl wrote: >>>> Am 12.10.2013 20:20, schrieb Serhiy Storchaka: >&g

Re: [Python-Dev] Support for marking limited API elements in C API docs

Am 12.10.2013 22:30, schrieb Antoine Pitrou: > On Sat, 12 Oct 2013 22:25:36 +0200 > Georg Brandl wrote: >> >> > ("limited API" is really a bad synonym for "stable ABI" IMO) >> >> >> >> It's not a synonym: to get a stable

Re: [Python-Dev] Bug tracker and docs@python

Am 17.10.2013 17:29, schrieb Benjamin Peterson: > 2013/10/17 Ethan Furman : >> Good day! >> >> What is the effect of assigning a bug tracker issue to docs@python? > > The assignee field is set to d...@python.org. > > In other words, nothing magical happens. Correct so far, but the point of the e

Re: [Python-Dev] cpython: Issue #16129: Add `Py_SetStandardStreamEncoding`

Am 17.10.2013 17:36, schrieb Antoine Pitrou: > On Thu, 17 Oct 2013 15:22:03 +0200 (CEST) > nick.coghlan wrote: >> >> +.. c:function:: int Py_SetStandardStreamEncoding(char *encoding, char >> *errors) >> + >> + .. index:: >> + single: Py_Initialize() >> + single: main() >> + tri

Re: [Python-Dev] Current Python 3.2 status?

On 06/11/2016 07:41 PM, Chi Hsuan Yen wrote: > > > On Sun, Jun 12, 2016 at 1:02 AM, Berker Peksağ > wrote: > > On Sat, Jun 11, 2016 at 8:59 AM, Chi Hsuan Yen > wrote: > > Hello all, > > > > Georg said in February th

Re: [Python-Dev] yield * (Re: Missing operator.call)

gl...@divmod.com schrieb: > On 01:00 am, greg.ew...@canterbury.ac.nz wrote: >>Guido van Rossum wrote: >>>We already have yield expressions and they mean something else... >> >>They don't have a "*" in them, though, and I don't >>think the existing meaning of yield as an expression >>would carry ove

Re: [Python-Dev] Tracker archeology

Daniel (ajax) Diniz schrieb: > Over-spammig: > Sorry, Georg! I only noticed all issues in the Documentation > component are auto-assigned to you today. This meant dozens of unasked > for assignments :-/ That's okay, I'll go through them at the weekend and just unassign what I won't manage to do

Re: [Python-Dev] Small misleadingness in docs

Raymond Hettinger schrieb: > [Greg Ewing] >> I've discovered something slightly misleading in the docs >> for PyObject_IsInstance: >> >> When testing if B is a subclass of A, if A is B, PyObject_IsSubclass >> returns true. If A and B are different objects, B's __bases__ >> attribute is search

Re: [Python-Dev] To 3.0.2 or not to 3.0.2?

Benjamin Peterson schrieb: > On Tue, Feb 17, 2009 at 5:25 AM, Samuele Pedroni wrote: >> Didn't a test fail because of this? seems the underlying issue is that this >> part of the stdlib didn't have enough test coverage. It seems that having >> very good/improving test coverage like is recommended

Re: [Python-Dev] To 3.0.2 or not to 3.0.2?

Benjamin Peterson schrieb: > On Tue, Feb 17, 2009 at 3:02 PM, Georg Brandl wrote: >> Benjamin Peterson schrieb: >>> On Tue, Feb 17, 2009 at 5:25 AM, Samuele Pedroni >>> wrote: >>>> Didn't a test fail because of this? seems the underlying issue is t

Re: [Python-Dev] A suggestion: Do proto-PEPs in Google Docs

Stephen J. Turnbull schrieb: > FWIW, Google Docs is almost there. Working with Brett et al on early > drafts of PEP 0374 was easy and pleasant, and Google Docs gives > control of access to the document to the editor, not the Subversion > admin. The ability to make comments that are not visible t

Re: [Python-Dev] IO implementation: in C and Python?

Antoine Pitrou schrieb: > Benjamin Peterson python.org> writes: >> >> As we prepare to merge the io-c branch, the question has come up [1] >> about the original Python implementation. Should it just be deleted in >> favor C version? The wish to maintain the two implementations together >> has bee

Re: [Python-Dev] Googlebot and the mail.python.org python-dev archive

Guido van Rossum schrieb: > I think the better syntax would be to add site:mail.python.org to the > query, but you're right, that doesn't seem to find recent messages. > Maybe the absence of a robots.txt file on mail.python.org could be a > partial explanation? Doesn't the absence of a robots.txt

Re: [Python-Dev] PEP 372 -- Adding an ordered directory to collections ready for pronouncement

Benjamin Peterson schrieb: > 2009/3/1 Armin Ronacher : >> Hi everybody, >> >> PEP 372 was modified so that it provides a simpler API (only the dict API >> to be exact) and it was decided to start with a Python-only implementation >> and replace it with a C version later if necessary. >> >> Annotate

Re: [Python-Dev] Integrate BeautifulSoup into stdlib?

James Y Knight schrieb: > On Mar 4, 2009, at 9:56 AM, Chris Withers wrote: > >> Vaibhav Mallya wrote: >>> We do have HTMLParser, but that doesn't handle malformed pages >>> well, and just isn't as nice as BeautifulSoup. >> >> Interesting, given that BeautifulSoup is built on HTMLParser ;-) > >

Re: [Python-Dev] running the tests...

Chris Withers schrieb: > Hi All, > > I found the very brief snippet on test-running at: > > http://python.org/dev/faq/#how-to-test-a-patch > > so thought I'd ask here: > > - what's the canonical way to run "all the tests"? Assuming UNIXy OSes: make test, or if you want to save a bit of tim

Re: [Python-Dev] What level of detail wanted for import and the language reference?

Benjamin Peterson schrieb: > 2009/3/16 Brett Cannon : >> At this point importlib is done for its public API for Python 3.1. That >> means it's time to turn my attention to making sure the semantics of import >> are well documented. But where to put all of the details? The language >> reference for

Re: [Python-Dev] Mercurial?

Dirkjan Ochtman schrieb: > On 05/04/2009 12:27, Antoine Pitrou wrote: >> There's also the issue of how we adapt the current workflow of "svnmerging" >> between branches when we want to back- or forward-port stuff. In particular, >> tracking of already done or blocked backports. > > Right. The cano

Re: [Python-Dev] Generator methods - "what's next" ?

Firephoenix schrieb: > Hello everyone > > I'm a little confused by the recent changes to the generator system... > > I basically agreed with renaming the next() method to __next__(), so as > to follow the naming of other similar methods (__iter__() etc.). > But I noticed then that all the other

Re: [Python-Dev] Mercurial?

Dirkjan Ochtman schrieb: > On 05/04/2009 20:36, "Martin v. Löwis" wrote: >> We do require full real names (i.e. no nicknames). Can Mercurial >> guarantee such a thing? > > We could pre-record the list of allowed names in a hook, then have the > hook check that usernames include one of those names

Re: [Python-Dev] Mercurial?

Dirkjan Ochtman schrieb: > On 05/04/2009 20:29, "Martin v. Löwis" wrote: >> FYI: this is the list of hooks currently employed: >> - pre: check whitespace >> - post: mail python-checkins >> inform regular buildbot >> inform community buildbot >> trigger website rebuild if

Re: [Python-Dev] Mercurial?

Antoine Pitrou schrieb: > Georg Brandl gmx.net> writes: >> >> When commits with bad whitespace changes are rejected on push, this is a >> pretty good incentive to run the pre-commit hook next time, so that you >> don't have to re-do all the commits in that bat

Re: [Python-Dev] Mercurial?

Martin v. Löwis schrieb: >>> We could pre-record the list of allowed names in a hook, then have the >>> hook check that usernames include one of those names and an email >>> address (so people can still start using another email address). >> >> What about commits from other people, e.g. pulled f

Re: [Python-Dev] FWD: Library Reference is incomplete

Thomas Wouters schrieb: > > Anyone able to look into this and fix it? Having all of the normal > entrypoints for documentation broken is rather inconvenient for users :-) A rebuild should do the trick, I'll fix this ASAP. Georg ___ Python-Dev mailing

Re: [Python-Dev] PyCFunction_* Missing

Campbell Barton schrieb: > Hi, Just noticed the new Python 2.6.2 docs now dont have any reference to > * PyCFunction_New > * PyCFunction_NewEx > * PyCFunction_Check > * PyCFunction_Call > > Ofcourse these are still in the source code but Im wondering if this > is intentional that these functions s

[Python-Dev] Python Bug Day on April 23

Hi, I'd like to announce that there will be a Python Bug Day on April 23. As always, this is a perfect opportunity to get involved in Python development, or bring your own issues to attention, discuss them and (hopefully) resolve them together with the core developers. We will coordinate over IRC

[Python-Dev] Correction: Python Bug Day on April 25

Hi, I managed to screw up the date, so here it goes again: I'd like to announce that there will be a Python Bug Day on April 25. As always, this is a perfect opportunity to get involved in Python development, or bring your own issues to attention, discuss them and (hopefully) resolve them togethe

Re: [Python-Dev] Correction: Python Bug Day on April 25

Maciej Fijalkowski schrieb: > On Wed, Apr 15, 2009 at 1:10 PM, Georg Brandl wrote: >> Hi, >> >> I managed to screw up the date, so here it goes again: >> >> I'd like to announce that there will be a Python Bug Day on April 25. > Are you aware that this

[Python-Dev] Reminder: Python Bug Day on Saturday

Hi, I'd like to remind everyoone that there will be a Python Bug Day on April 25. As always, this is a perfect opportunity to get involved in Python development, or bring your own issues to attention, discuss them and (hopefully) resolve them together with the core developers. We will coordinate

Re: [Python-Dev] PyEval_Call* convenience functions

Tim Lesher schrieb: > Is there a reason that the PyEval_CallFunction() and > PyEval_CallMethod() convenience functions remain undocumented? (i.e., > would a doc-and-test patch to correct this be rejected?) > > I didn't see any mention of this coming up in python-dev before. > > Also, despite its

[Python-Dev] multi-with statement

Hi, this is just a short notice that Mattias Brändström and I have finished a patch to implement the previously discussed and mostly warmly welcomed extension to with's syntax, allowing with A() as a, B() as b: to be written instead of with A() as a: with B() as b: This syntax was

Re: [Python-Dev] multi-with statement

Fredrik Johansson schrieb: > On Sat, May 2, 2009 at 9:01 PM, Georg Brandl wrote: >> Hi, >> >> this is just a short notice that Mattias Brändström and I have finished a >> patch to implement the previously discussed and mostly warmly welcomed >> extension to with&

Re: [Python-Dev] special method lookup: how much do we care?

Benjamin Peterson schrieb: > A while ago, Guido declared that all special method lookups on > new-style classes bypass __getattr__ and __getattribute__. This almost > completely consistent now, and I've been working on patching up a few > incorrect cases. I've know hit __enter__ and __exit__. The c

Re: [Python-Dev] PEP 384: Defining a Stable ABI

Martin v. Löwis schrieb: > Header Files and Preprocessor Definitions > - > > Applications shall only include the header file Python.h (before > including any system headers), or, optionally, include pyconfig.h, and > then Python.h. What about structmember.

Re: [Python-Dev] cleanup before 3.1 is released

Neal Norwitz schrieb: > Has anyone run valgrind/purify and pychecker/pylint on the 3.1 code > recently? Both sets of tools should be used before the final release > so we can fix any obvious problems. Do pychecker/pylint work on 3.x code? Gerog -- Thus spake the Lord: Thou shalt indent with f

Re: [Python-Dev] Issues with Py3.1's new ipaddr

Benjamin Peterson schrieb: > 2009/6/2 Guido van Rossum : >> Benjamin, what would be involved in removing it? I suppose there's the >> module itself, some unit tests, and some docs. (I'm not asking you to >> remove it yet -- but I'm asking to look into the consequences, so that >> we can be sure to

Re: [Python-Dev] Draft PEP 385: Migrating from svn to Mercurial

Antoine Pitrou schrieb: > Dirkjan Ochtman ochtman.nl> writes: >> >> http://www.python.org/dev/peps/pep-0385/ > > « [cloned branches] makes it easier to distinguish branches, at the expense of > requiring more disk space on the client. » > > This is a bit misleading. Actually, by separating bran

Re: [Python-Dev] Roundup keywords for bug tracking

Daniel Diniz schrieb: > anatoly techtonik wrote: >> >> It is impossible to edit roundup keywords and this takes away the >> flexibility in selecting bugs related to a module/function/test or >> some other aspect of development. For example, I need to gather all >> subprocess bugs in one query and t

Re: [Python-Dev] Draft PEP 385: Migrating from svn to Mercurial

Frank Wierzbicki schrieb: > At PyCon, we discussed moving Jython's svn repository to Python's with > Martin von Löwis. I would think that Jython would live in Python's hg > repository in the same way as stackless and distutils. Has the > parallel project strategy been determined? Will they be se

Re: [Python-Dev] Draft PEP 385: Migrating from svn to Mercurial

Frank Wierzbicki schrieb: > On Mon, Jun 8, 2009 at 11:32 AM, Dirkjan Ochtman wrote: >> I'd say migrating to Python's svn doesn't make a whole lot of sense at >> this point, but I'll leave that to Martin (since he has to do the >> work). For the conversion, I can just as well take the Jython repo >>

Re: [Python-Dev] draft pep: backwards compatibility

Benjamin Peterson schrieb: > Backwards compatibility seems to be an issue that arises a lot here. I > think we all have an idea of it is, but we need some hard place to > point to. So here's my attempt: Yet another rather pointless bikeshed: if this becomes policy, maybe it should get a PEP number

Re: [Python-Dev] draft pep: backwards compatibility

R. David Murray schrieb: > On Fri, 19 Jun 2009 at 14:15, Antoine Pitrou wrote: > >> Benjamin Peterson python.org> writes: >>> >>> I mean that if you pass X and Y into a function and get Z in 2.6, then >>> you should be able to get Z from passing X and Y in 2.7 even if >>> there's a new argument t

Re: [Python-Dev] Adding syntax for units of measure

Tobias C. Rittweiler schrieb: > Hi! > > Has anyone added special syntax to allow writing numeric literals with > physical units? So you can write 12m + 34cm, and would get 12.34m. > > My question is how would you modify the BNF the most sensible way to > allow for this? The above example is simpl

Re: [Python-Dev] [RELEASED] Python 3.1 final

Benjamin Peterson schrieb: > On behalf of the Python development team, I'm thrilled to announce the first > production release of Python 3.1. Congrats! Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and t

Re: [Python-Dev] Mercurial migration: progress report (PEP 385)

Dirkjan Ochtman schrieb: > - Fifth, here's a list of things, off the top of my head, that still need > doing: > > * Get agreement on branch strategy and branch processing (list of > branches + proposed handling at > http://hg.python.org/pymigr/file/tip/all-branches.txt) <--- PLEASE > REVIEW Do

Re: [Python-Dev] Mercurial migration: progress report (PEP 385)

Martin v. Löwis schrieb: >> We could add another value in the tuple that specifies the VCS: >> ('CPython', 'branches/release25-maint', '61464', 'svn'). I agree that >> VCSs are not universally the same, but the concept of a revision is >> universal. > > Actually, I think that's not the case. For b

Re: [Python-Dev] Mercurial migration: progress report (PEP 385)

Martin v. Löwis schrieb: >> It will handle it, for sure, but I think it would all go easier if we >> could work with stricter subset branches (and leave the effective >> cherrypicking for the occasional problem). > > So I think the PEP should propose a workflow (or: merge flow) if you > think we w

[Python-Dev] Document None values in sys.modules?

Hi all, is the presence of None values in sys.modules considered an implementation detail? If not, it should be documented what the None values mean to the interpreter. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou s

Re: [Python-Dev] Update to Python Documentation Website Request

David Lyon schrieb: > On Fri, 24 Jul 2009 03:23:57 +0200, Christian Heimes > wrote: >> I'm sorry to inform you that a wxWindows based solution has zero change >> to get into the Python standard library ever. We are not going to add >> another GUI toolkit to the core distribution. > > In executab

Re: [Python-Dev] PEP 385: the eol-type issue

Neil Hodgson schrieb: > Martin v. Löwis: > >> Or don't you understand why that single unresolved item didn't manage >> to revert the decision? Well, there are many unresolved items in >> the Mercurial conversion, some much more stressful than the eol issue >> (e.g. the branching discussion). > >

Re: [Python-Dev] PEP 385: the eol-type issue

Stephen J. Turnbull schrieb: > Mark Hammond writes: > > > I'm not sure what point you are trying to make, but I believe it *is* > > possible for a solution to be found here which will keep Windows users > > happy. I'm guessing you haven't had much practical experience with this > > proble

Re: [Python-Dev] PEP 385: the eol-type issue

Martin v. Löwis schrieb: >> I'm not aware of any other unresolved items; they may exist, but the fact >> that they're not discussed on this list in detail means that they are >> largely unimportant. > > There is a long list of things that still need to be done; each one > potentially creating new

Re: [Python-Dev] standard library mimetypes module pathologically broken?

Nick Coghlan schrieb: > Nick Coghlan wrote: >> Benjamin Peterson wrote: >>> >>> If python-dev was more interested, we would have a policy for this. *cough* >>> >> >> PEP 5 isn't enough? (I'll grant that PEP could probably do with >> mentioning the use of warnings.warn(DeprecationWarning) explici

Re: [Python-Dev] test failure on py3k branch in test___all__

Chris Withers schrieb: > Hi All, > > Anyone know what's causing this failure? > > test test___all__ failed -- Traceback (most recent call last): >File "Lib/test/test___all__.py", line 106, in test_all > self.check_all("profile") >File "Lib/test/test___all__.py", line 23, in check_all

Re: [Python-Dev] Mercurial migration: help needed

Martin v. Löwis schrieb: >> I don't think this problem is really serious. >> If the push fails, you can just commit (locally) a new changeset that >> repairs the EOL or indentation problems > > I would find that unfortunate. It's a fairly irrelevant change, yet > it may manage to corrupt the histo

[Python-Dev] displayhook behavior in pdb

May I have a short vote on this issue: http://bugs.python.org/issue6903 In short, pdb (since 2.6) uses a separate displayhook in order to avoid _ being reassigned (which screws up debugging apps that use _ as gettext). In that displayhook, I did not add the suppression of printing None, as it

Re: [Python-Dev] displayhook behavior in pdb

Guido van Rossum schrieb: > >> Now, what is the lesser evil? > >> > >> > > > > IMO not showing the extraneous Nones is preferable. > > I agree (although I don't use pdb, so my view shouldn't be given too > much weight...) > > > I *do* use pdb a lot, and I agree that

Re: [Python-Dev] Misc/maintainers.rst

R. David Murray schrieb: > I floated a proposal on stdlib-sig to create a file named > Misc/maintainers.rst. The purpose of this file is to collect knowledge > about who knows which modules well enough to make decision about issues > in the tracker when the participants in the issue aren't sure, a

Re: [Python-Dev] Misc/maintainers.rst

A.M. Kuchling schrieb: > On Thu, Sep 17, 2009 at 07:38:50PM +0200, Georg Brandl wrote: >> So the plan would be to consolidate these into another set of rst docs, >> having them in the repo, editable by every committer, as well as published >> somewhere on python.org (devdocs.p

Re: [Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations

Chris Withers schrieb: > Jared Flatow wrote: >> This might help: >> >> http://mail.python.org/pipermail/python-dev/2008-June/080111.html >> >> Here is the most relevant part (quoting Guido): >> >> > Does it help if I tell you that for "x y" we always try >> > x.__binop__(y) before trying y.__

Re: [Python-Dev] transitioning from % to {} formatting

Bugbee, Larry schrieb: >>> Do the users get any say in this? >> >> I'm a user! :-) >> >> I hate calling methods on string literals, I think it looks very odd to >> have code like this: >> >> "Displaying {0} of {1} revisions".format(x, y) > > Ugh! Good point. > > Is Python to be an easy-to-lea

Re: [Python-Dev] eggs now mandatory for pypi?

Jesse Noller schrieb: > On Mon, Oct 5, 2009 at 4:43 AM, Fredrik Lundh wrote: >> it's revews like this that makes me wonder if releasing open source is >> a good idea: >> >> no egg - worst seen ever, remove it from pypi or provide an egg >> (jensens, 2009-10-05, 0 points) >> >> > > Unfortunatel

Re: [Python-Dev] no consensus on static metadata

Chris Withers schrieb: > Tarek Ziadé wrote: >>> NB: There was no consensus on this "micro-language" on distutils-sig. >>> While I suspect I don't care as none of my packages rely on anything other >>> than other python packages, others did care, and I found the syntax Tarek >>> was proposing pretty

Re: [Python-Dev] BDFL pronouncement?

Chris Withers schrieb: > Guido van Rossum wrote: >> I'm saying that I don't expect setuptools 0.7 to appear before Tarek's >> Distribute is mature and in widespread use. IOW I support Tarek's fork >> and suggest nobody hold their breath waiting for setuptools 0.7. > > Well, if this was the BDFL pr

Re: [Python-Dev] Top-posting on this list

Benjamin Peterson schrieb: > 2009/10/11 Jesse Noller : >> On Sun, Oct 11, 2009 at 12:38 PM, Stephen J. Turnbull >> wrote: >> >>> If others are willing to play bad cop, as Aahz did, I'd be very happy >>> to accept the benefit of a cleaned-up list. But I'm not willing to do >>> it myself. >> >> Is

[Python-Dev] http://www.pythonlabs.com/logos.html is gone

Which I noticed since it's cited in the BeOpen license we still refer to in LICENSE. Since pythonlabs.com itself is still up, it probably isn't much work to make the logos.html URI work again, but I don't know who maintains that page. cheer, Georg -- Thus spake the Lord: Thou shalt indent with

Re: [Python-Dev] http://www.pythonlabs.com/logos.html is gone

Guido van Rossum schrieb: > On Sun, Oct 11, 2009 at 12:55 PM, Georg Brandl wrote: >> Which I noticed since it's cited in the BeOpen license we still refer >> to in LICENSE. Since pythonlabs.com itself is still up, it probably >> isn't much work to make the logos.h

Re: [Python-Dev] Interest in integrating C decimal module into Python?

ecimal > specification: I'm not sure that functions like exp, log and log10 > are currently working. Georg Brandl might know better than I do. I haven't touched that code since the sprint, but a student named Mateusz Rukowicz worked on it for a past Summer of Code, I think. I n

[Python-Dev] PyErr_NewExceptionWithDoc

Hi, issue #7033 proposes a new C API that creates a new exception class with a docstring. Since exception classes should be documented, and adding the docstring after creating is not a one-liner, I would say it is a useful addition. What do you all think? Georg -- Thus spake the Lord: Thou sh

Re: [Python-Dev] Bug 7183 and Python 2.6.4

Tres Seaver schrieb: > Barry Warsaw wrote: >> On Oct 22, 2009, at 10:47 AM, Benjamin Peterson wrote: > >>> 2009/10/22 Barry Warsaw : So does anybody else think bug 7183 should be a release blocker for 2.6.4 final, or is even a legitimate but that we need to fix? >>> I think it can

Re: [Python-Dev] Retrieve an arbitrary element from a set without removing it

Chris Bergstresser schrieb: >I like the proposed set.get() method, personally. list.get(index) > gets the item at that index, dict.get(key) gets the item associated > with that key, set.get() gets an item, but doesn't place any > guarantees on which item is returned. Sorry to nitpick, but th

Re: [Python-Dev] Retrieve an arbitrary element from a set without removing it

Chris Bergstresser schrieb: > On Tue, Oct 27, 2009 at 11:06 AM, Georg Brandl wrote: >> Sorry to nitpick, but there is no list.get(). > >No? How ... odd. I guess it wouldn't have come up, but I was sure > there was a .get method which took an optional default paramete

Re: [Python-Dev] Retrieve an arbitrary element from a set withoutremoving it

Steven D'Aprano schrieb: > On Wed, 28 Oct 2009 04:47:59 am Raymond Hettinger wrote: > >> A dict.get() can be meaningfully used in a loop (because the key can >> vary). A set.get() returns the same value over and over again >> (because there is no key). > > I don't believe anyone has requested tho

Re: [Python-Dev] 2.7 Release? 2.7 == last of the 2.x line?

Martin v. Löwis schrieb: >> It's pretty easy to make Python source that works under 2.6 and 3.x. >> It's basically impossible to make Python source that works under 2.4/2.5 >> and 3.x. You may be able to write code that works under 2.4/2.5 and >> works cleanly with 2to3 to produce 3.x code. I ha

Re: [Python-Dev] 2.7 Release? 2.7 == last of the 2.x line?

Raymond Hettinger schrieb: > [Michael Foord] >> What will it take to *start* the port? (Or is it already underway?) For >> many projects I fear that it is only the impending obsolescence (real >> rather than theoretical) of Python 2 that will convince projects to port. > > FWIW, I do not buy into

Re: [Python-Dev] 2.7 Release? 2.7 == last of the 2.x line?

sstein...@gmail.com schrieb: > > On Nov 3, 2009, at 12:28 PM, Arc Riley wrote: >> >> The main thing holding back the community are lazy and/or obstinate >> package maintainers. If they spent half the time they've put into >> complaining about Py3 into actually working to upgrade their code >> the

Re: [Python-Dev] 2.7 Release? 2.7 == last of the 2.x line?

Antoine Pitrou schrieb: > Georg Brandl gmx.net> writes: >> >> skip pobox.com schrieb: >> > Martin> And if *2.6* becomes the last of the 2.x series? >> > >> > With all due respect, I don't think you can make that decision now. The >

Re: [Python-Dev] 2.7 Release? 2.7 == last of the 2.x line?

Terry Reedy schrieb: > James Y Knight wrote: > >> If that happens, it's not true that there's *nowhere* to go. A solution >> would be to discard 3.x as a failed experiment, take everything that is >> useful from it and port it to 2.x, and simply continue development from >> the last 2.x release

Re: [Python-Dev] 2.7 Release? 2.7 == last of the 2.x line?

s...@pobox.com schrieb: > Martin> And if *2.6* becomes the last of the 2.x series? > > With all due respect, I don't think you can make that decision now. The > time to have stated 2.6 would be the end of the 2.x line was when 2.6 was > released. At that point instead of opening up the trunk

Re: [Python-Dev] PEP 3003 - Python Language Moratorium

exar...@twistedmatrix.com schrieb: > On 12:10 pm, s...@pobox.com wrote: >>Guido> ... it's IMO pretty mysterious if you encounter this and >>don't >>Guido> already happen to know what it means. >> >>If you require parens maybe it parses better: >> >>import (a or b or c) as mod >> >>Give

Re: [Python-Dev] OpenSSL vulnerability

Guido van Rossum schrieb: > On Fri, Nov 6, 2009 at 2:36 PM, wrote: >> Also, for Python 2.5 and earlier, any SSL-based code is vulnerable to a MitM >> anyway, so this can only be an issue for code using the new APIs in Python >> 2.6. > > That's not going to stop the > wannabe-self-proclaimed-so-c

Re: [Python-Dev] PEP 3003 - Python Language Moratorium

Gregory P. Smith schrieb: > On Thu, Nov 5, 2009 at 4:13 PM, Yuvgoog Greenle wrote: >> On Fri, Nov 6, 2009 at 1:55 AM, Bobby R. Ward wrote: >>> >>> A switch to ENABLE those warnings? >>> >> >> I think a few people I know would still be raising strings like exceptions >> if not for the deprecation

Re: [Python-Dev] PEP 3003 - Python Language Moratorium

A.M. Kuchling schrieb: > On Sun, Nov 08, 2009 at 10:27:46PM +0100, Georg Brandl wrote: >> Good point, I'll make that change if AMK agrees. > > It's certainly fine with me. Do we want to only make that change to > the 2.7 "What's New", or should we also

Re: [Python-Dev] IDLE as default Python editor

Nick Coghlan schrieb: > Martin v. Löwis wrote: >> Nick Coghlan wrote: >>> Ben Finney wrote: anatoly techtonik writes: > Quite an interesting question recently popped up in pygame community > that I'd like to ask to Python developers. This forum is specifically about developm

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

Sriram Srinivasan schrieb: > I guess why every programming language has some kind of a 'standard > library' built in within it. In my view it must not be called as a > 'library' at all. what it does > is like a 'bunch of built-in programs ready-made to do stuff'. > > Lets see what a 'library' does

Re: [Python-Dev] PyPI comments and ratings, *really*?

R. David Murray schrieb: > On Thu, 12 Nov 2009 at 15:42, Terry Reedy wrote: >> Part of the pypi problem is a startup problem of initially low numbers. If >> the only people who bother to log in to rate are the disgruntled, then the >> ratings/reviews will be biased. I wonder how many of the peopl

Re: [Python-Dev] PyPI comments and ratings, *really*?

Ben Finney schrieb: > Michael Sparks writes: > >> On Fri, Nov 13, 2009 at 12:44 AM, Ben Finney >> wrote: >> > So, the poll's audience is limited to those who visit the front page >> > (which is hardly ever necessary for package maintainers), and those >> > who already know it exists (e.g. throu

Re: [Python-Dev] buildtime vs runtime in Distutils

Antoine Pitrou schrieb: > Tarek Ziadé gmail.com> writes: >> >> This cannot work on all platforms, when our Makefile is not shipped >> with python but python-devel. (like Fedora) > > This practice is stupid anyway, because it means you have to install > python-devel even to install pure Python pa

Re: [Python-Dev] Status of the Buildbot fleet and related bugs

Martin v. Löwis schrieb: >> Yes, I think this just started happening. I'm guessing that the main >> site proxies the buildbot URL requests to the buildbot master process, >> and when it's down you get the 404s from the main server. >> >> I figured someone might be working on the master, though per

<    1   2   3   4   5   6   7   8   9   10   >