On Thu, Nov 12, 2020 at 8:49 PM Guido van Rossum wrote:
> The correct place for the docs for __cause__ and __context__ is in the
> section in the library reference about exceptions. There's quite a bit
> about them there already. That's where the tutorial should link as well.
>
> And now I ask yo
On Wed, Nov 18, 2020 at 7:04 PM Daniel Moisset wrote:
> [sorry for the duplicate, meant to reply-all]
>
> Thank you for this approach, I find it really helpful to put the
> conversation in these terms (semantics and guiding principles).
>
> It does help to rationalise discussion ;-)
> [...]
> 4.
On Wed, Nov 18, 2020 at 7:45 PM Brett Cannon wrote:
>
>
> On Tue, Nov 17, 2020 at 10:16 PM Greg Ewing
> wrote:
>
>> On 18/11/20 4:36 pm, Larry Hastings wrote:
>> >
>> > But,
>> > the thinking went, you'd never want to examine the last value from a
>> > list generator, so it was more convenient i
On Thu, Nov 19, 2020 at 8:08 PM Brett Cannon wrote:
>
>
> On Thu, Nov 19, 2020 at 5:16 AM Steve Holden wrote:
>
>> On Wed, Nov 18, 2020 at 7:04 PM Daniel Moisset
>> wrote:
>>
>>> [sorry for the duplicate, meant to reply-all]
>>>
>>> Tha
Fair enough.
On Fri, Nov 20, 2020 at 11:45 AM Thomas Wouters wrote:
>
>
> On Fri, Nov 20, 2020 at 8:38 AM Steve Holden wrote:
>
>> On Thu, Nov 19, 2020 at 8:08 PM Brett Cannon wrote:
>>
>> All I will say is just because we aren't *required* to implement it
A general wish not to disadvantage those with older hardware any more than
they already are?
Just a shot in the dark.
On Wed, Dec 9, 2020 at 6:17 PM Gregory P. Smith wrote:
>
>
> As a meta question: Is there a good reason to support binaries running on
> macOS earlier than ~ $latest_version-1?
If the length of the name is any kind of issue, since the stdlib
only contains modules (and packages), why not just sys.stdlib_names?
On Mon, Jan 25, 2021 at 5:18 PM Victor Stinner wrote:
> Hi Bernat,
>
> "stdlib_module_names" was my first idea but it looks too long, so I
> chose "module_names"
My suggestion that it be introduced via __future__ due to its contentious
nature met immediate resistance. No point going down that road.
Kind regards,
Steve
On Sat, Feb 6, 2021 at 8:15 PM Ivan Pozdeev via Python-Dev <
python-dev@python.org> wrote:
> With such a large new area of functionality
ed in
> the discussions.
> On 06.02.2021 23:58, Steve Holden wrote:
>
> My suggestion that it be introduced via __future__ due to its contentious
> nature met immediate resistance. No point going down that road.
>
> Kind regards,
> Steve
>
>
> On Sat, Feb 6, 2021 at
On Fri, Feb 19, 2021 at 10:53 PM Christian Heimes
wrote:
> On 19/02/2021 23.22, Stestagg wrote:
> > The thing that stood out from this conversation, for me, is: Releases
> > are too hard, and there’s a risk of not having enough volunteers as a
> > result.
> >
> > How hard is it to fix that?
>
> A
The old rule is best: be strict in what you produce and liberal i what you
accept.
Kind regards,
Steve
On Tue, Apr 13, 2021 at 12:52 AM Edwin Zimmerman
wrote:
> On 4/12/2021 6:34 PM, Brett Cannon wrote:
>
> Had the sentences ended at "confusing" or said something like "I don't
> think it's as
DEFAULT_TIMESTAMP?
Kind regards,
Steve
On Wed, Apr 14, 2021 at 8:03 PM wrote:
> If the so, then a better name than NO_TIMESTAMP should be chosen, as the
> gzip specification does not allow for no timestamp.
> ___
> Python-Dev mailing list -- python-d
On Fri, Apr 16, 2021 at 7:15 PM Denis Kotov wrote:
> Ethan Furman wrote:
> > On 4/16/21 10:43 AM, redrad...@gmail.com wrote:
> > > Take a look at this video https://www.youtube.com/watch?v=D7Sd8A6_fYU
> > > or read some articles ... otherwise I will need to spend too many time
> providing evidenc
On Thu, May 13, 2021 at 9:18 AM Mark Shannon wrote:
> Hi Terry,
>
> On 13/05/2021 5:32 am, Terry Reedy wrote:
> > On 5/12/2021 1:40 PM, Mark Shannon wrote:
> >
> >> This is an informational PEP about a key part of our plan to improve
> >> CPython performance for 3.11 and beyond.
> >
> >> As alway
On Thu, May 13, 2021 at 11:07 PM Steven D'Aprano
wrote:
> Steve
> (one of the other ones)
>
We are all other Steves!
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.or
On Fri, May 28, 2021 at 10:26 PM Ethan Furman wrote:
> On 5/28/21 12:43 AM, Petr Viktorin wrote:
> > On 28. 05. 21 5:24, Ethan Furman wrote:
>
> >> class FlagWithMasks(IntFlag):
> >> DEFAULT = 0x0
> >>
> >> FIRST_MASK = 0xF
> >> FIRST_ROUND = 0x0
> >>
On Fri, Jul 2, 2021 at 12:47 AM wrote:
> Okay so I just code a little bit and I used the multiprocessing module but
> my code didn't work and I found the solution on Stack Overflow and it
> turned out to be not my mistake (which has never happened before I think).
> Instead I found out it's a bug
On Wed, Aug 11, 2021 at 2:27 PM Guido van Rossum wrote:
> As it happens, I have a working prototype of lazy in marshaling that would
> work well for this.
>
> Nice to see you keep the time machine in working order ...
Kind regards,
Steve
___
Python-Dev
On Wed, Aug 11, 2021 at 7:09 AM Larry Hastings wrote:
> On 8/10/21 11:15 AM, Thomas Grainger wrote:
>
> Although the co_annoations code could intercept the NameError and replace
> return a ForwardRef object instead of the resolved name
>
>
> No, it should raise a NameError, just like any other P
Your inflated sense of your own significance is unfortunate, since it
appears to prohibit you from considering the possibility you might have
made a rather silly mistake here, and one which is calculated to move you
further away from your stated goals.
Kind regards,
Steve
On Tue, Aug 17, 2021 at
You forgot:
5. When I just don't damned well feel like it.
Kind regards,
Steve
On Wed, Aug 25, 2021 at 8:25 PM Brett Cannon wrote:
> I just wanted to apologize for any angst or noise my replies to Marco
> caused folks. I should have known that correcting Marco on how to address
> me would hav
I suspect it's the same motivation that makes us comment out a block of
code rather than deleting it, even though we know the VCS will let us
retirive it whenever we want. If I'm wrong it won't be fatal. Or surprising
;-)
Kind regards,
Steve
On Wed, Aug 25, 2021 at 8:53 PM Eric V. Smith wrote:
I understood that _iterables_ are required to have an __iter__ method, not
iterators.
Therefore, are we simply discussing whether all iterators should be
iterable? At the moment the CPython implementation does't require that
AFAIK.
regards
Steve
On Tue, Sep 14, 2021 at 8:39 PM Guido van Rossum
Hi Peter,
While the humble webmasters can do little about this it's possible the
developers can, so I am forwarding your email to their mailing list.
regards
Steve
Steve Holden
On Tue, Jul 5, 2016 at 3:30 AM, Peter via Webmaster
wrote:
> Hi
> I'm a heavy user of Python
list, and the release manager may
or may not choose to update the published version.
regards
Steve
Steve Holden
On Fri, Sep 9, 2016 at 3:37 PM, Karen Little <
karen.lit...@whoishostingthismail.com> wrote:
> Hi,
>
> Just wanted to let you know about a link that seems to be broken
On Sat, Sep 10, 2016 at 6:57 PM, Nick Coghlan wrote:
> P.S. Although in this case, it may have just been a direct link to the
> 3.2 version of the 3.2 What's New - there isn't a lot we can do about
> that, as when a branch goes unsupported, we usually stop updating the
> docs as well (even when e
, difflib, random) do use this
technique, but it is far from universal.
So I thought it would be useful to get input from current devs about the
value of this practice, since to me it seems somewhat anti-pythonic. What
advantages does it confer?
regards
Steve Holden
the very clear explanation.
Would an addition to the documentation for 3.6 giving an abbreviated
version help while the devs consider whether any changes are appropriate
for 3.7?
Steve Holden
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.pyt
pattern matching. If re has advantages in certain situations someone might
upgrade the 3.x implementation and provide it as a 3rd-party module, though
the effort involved would be significant, so someone would have to be
motivated to keep it.
regards
Steve
Steve Holden
On Sun, Jan 29, 2017 at 4:13
n't troubled by correspondence on that
topic.
I applaud your efforts to build a Python community from the ground up, and
wish your efforts every success. I imagine there are other developers who
feel similarly.
regards
Steve
Steve Holden
On Mon, May 22, 2017 at 8:59 PM, Victor Njunu wrote:
> D
et and read the documentation there for
> installing buildbot.
>
I've added a note to the Wiki page informing readers of the preferred
link. S
Steve Holden
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listi
adequate justification for breaking public APIs that
> have been around for years."
My only question is "what's a variable called _source doing in the public
API?"
regards
Steve
Steve Holden
___
Python-Dev mailing list
Pyth
Makes sense. Thanks. S
Steve Holden
On Mon, Jul 17, 2017 at 4:29 PM, Raymond Hettinger <
raymond.hettin...@gmail.com> wrote:
>
> > On Jul 17, 2017, at 8:22 AM, Steve Holden wrote:
> >
> > My only question is "what's a variable called _source doing in the
Speaking as the author of the doc pages, I think I can safely say that
anyone who was smart enough to use asyncore/asychat back in the day (I used
it in "Python Web Programming") is almost certainly smart enough to have
migrated away from them long ago. They were an interesting approach to
asynchro
On Mon, Nov 15, 2021 at 8:42 AM Kyle Stanley wrote:
> On Sat, Nov 13, 2021 at 5:04 PM wrote:
>
>>
>>
>> def 𝚑𝓮𝖑𝒍𝑜():
>>
> [... Python code it's easy to believe isn't grammatical ...]
> return ₛ
>>
>
> 0_o color me impressed, I did not think that would be legal syntax. Would
> be interesting
On Tue, Nov 30, 2021 at 5:05 PM Steven D'Aprano wrote:
> On Tue, Nov 30, 2021 at 02:30:18PM +, Paul Moore wrote:
> [...]
> Aside: I'm a little disappointed in the way the typing ecosystem has
> developed. What I understood was that we'd get type inference like ML or
> Haskell use, so we would
On Tue, Jan 11, 2022 at 6:24 PM Guido van Rossum wrote:
> I personally think F-strings should not be usable as docstrings. If you
> want a dynamically calculated docstring you should assign it dynamically,
> not smuggle it in using a string-like expression. We don't allow "blah {x}
> blah".format
Time for a __legacy__ package?
Kind regards,
Steve
On Sun, Mar 27, 2022 at 7:06 PM Paul Moore wrote:
> On Sun, 27 Mar 2022 at 17:11, Christopher Barker
> wrote:
> >
> > With the json package included, all they need to do is `import json`. If
> that wasn't there, they's look in PyPi for a JSON
Not defining the semantics of annotations was a brave move, but
inevitably led to the situation where different use cases, all
quite reasonable, would spring into being. Now they have, the development
team has to decide a) which ones to sanction and b) which will be left out
in the cold.
I wish th
On Mon, Apr 4, 2022 at 4:13 PM Coyot Linden (Glenn Glazer) <
co...@lindenlab.com> wrote:
> I would like to point out another use case of triple quotes outside of
> docstrings. We do a lot of SQL here and so doing a parameterized query
> like:
>
> """SELECT foo
> FROM bar
> WHERE baz = %s"""
>
> is
I don't remember it being mentioned, but much of the traffic recently
migrated from this list to https://discuss.python.org/c/core-dev/23, which
you may wish to keep in touch with.
Kind regards,
Steve
On Tue, Oct 25, 2022 at 7:53 AM Juan Cristóbal Quesada <
rainonthescarecrowhumanwhe...@gmail.co
Well, the first comment is that this isn't really the best list to ask such
questions on, since it was created for the Python developers to discuss the
development of the language and its implementation. Further, such
discussions nowadays take place on discuss.python.org, and you can find
more info
Hi Chris,
Nice to see you on the list.
While this is definitely off-topic, I trust I might be given license by the
list's few remaining readers to point out that the match-case construct is
for _structural_ pattern matching. As I wrote in the latest Nutshell:
"Resist the temptation to use match u
Sounds like you might want the "Python Help" group on https;//
discuss.python.org - the dev conversation migrated there quite a while ago
now, so thighs channel is more or less announcements only.
Good luck with your project!
Kind regards,
Steve
On Thu, 5 Oct 2023 at 16:07, Guenther Sohler
wro
On Mon, 13 Nov 2023 at 10:18, Marc-Andre Lemburg wrote:
> [...]
>
> Question: Should we retire and archive this mailing list ?
> (I'm asking as one of the maintainers of the ML)
>
> [...]
Hi Marc-Andre,
Maybe just require senders to be members of the python.org domain, and
retain the release an
paring the ground for the eventual introduction of the syntax error.
Steve Holden
On Sat, Aug 10, 2019 at 8:07 AM Serhiy Storchaka
wrote:
> 10.08.19 02:04, Gregory P. Smith пише:
> > I've merged the PR reverting the behavior in 3.8 and am doing the same
> > in the master branc
On Mon, Aug 12, 2019 at 6:26 PM Terry Reedy wrote:
> On 8/8/2019 5:31 AM, Dima Tisnek wrote:
> [...]
>
> To me, this one of the major problems with the half-baked default.
> People who want string literals left as is sometimes get away with
> omitting explicit mention of that fact, but sometimes
e it of further traffic.
Good luck!
Steve Holden
On Fri, Aug 16, 2019 at 11:04 AM Ana Simion via Webmaster <
webmas...@python.org> wrote:
> Hello,
>
> Can you advise when you’re going to update Python to work with Mac OS X
> Catalina? I am running the beta of Mac OS X Catalina but
It's not dead, it's just restin' after a particularly heavy release process.
regards
Steve Holden
On Mon, Sep 9, 2019 at 4:24 PM Rhodri James wrote:
> On 09/09/2019 15:51, brian.sk...@gmail.com wrote:
> > it's getting better?
>
> No it
ishes,
Steve Holden
On Tue, Oct 29, 2019 at 10:59 PM Oz Tiram wrote:
> Hello Python-devs,
>
> The csv module is probably heavily utilized by newcomers to Python, being
> a very popular data exchange format.
> Although, there are better tools for processing tabular data like SQLite,
&g
If using a dictionary but still requiring attribute access, techniques such
as those used at https://github.com/holdenweb/hw can be used to simply
client code.
Kind regards,
Steve Holden
On Wed, Oct 30, 2019 at 11:15 AM Oz Tiram wrote:
> Hi Steve,
>
> Thanks for your reply. While
In which case, wouldn't "_" make a better literal prefix than "i"?
A better comparison might be between _"..." and f"...".
regards
Steve Holden
On Thu, Dec 5, 2019 at 5:37 AM Serhiy Storchaka wrote:
> 04.12.19 16:02, Anders Munch пише:
>
I've verified this fix and changed the status to "commit review." I trust
that was the correct action.
Kind regards,
Steve Holden
On Thu, Jan 9, 2020 at 9:57 PM Cédric Krier via Python-Dev <
python-dev@python.org> wrote:
> Hi,
>
> Any chance to get this P
Really webmas...@python.org would have been more appropriate, but I've
already copied that address on my direct reply to you. The python-dev list
is for discussions about the development of the language and its CPython
implementation.
Kind regards,
Steve
On Tue, Jan 28, 2020 at 7:20 PM
The webmaster list sends an auto-response to new posters. If something like
that could happen on python-dev too, as long as the advice was clear enough
the list could then simply ignore such requests, knowing that the
auto-responder had taken care of it. This could drive posters to
python-list or p
On Wed, Mar 25, 2020 at 5:42 PM Dennis Sweeney
wrote:
> I'm removing the tuple feature from this PEP. So now, if I understand
> correctly, I don't think there's disagreement about behavior, just about
> how that behavior should be summarized in Python code.
> [...]
> return (the original obje
On Mon, Apr 6, 2020 at 8:04 PM Guido van Rossum wrote:
> On Mon, Apr 6, 2020 at 11:36 AM Steven D'Aprano
> wrote:
>
>>
>> Personally, I would not like to have to explain to newcomers why `match`
>> is a keyword but you can still use it as a function or variable, but not
>> other keywords like `r
On Wed, May 20, 2020 at 7:11 PM Jim J. Jewett wrote:
> David Mertz wrote:
>
> > Fwiw, I don't think it changes my order, but 'strict' is a better word
> than
> > 'equal' in all those places. I'd subtract 0.1 from each of those votes if
> > they used "equal".
>
> I would say that 'equal' is worse
It's broadly accepted among professional writers that the language used
should be acceptable and comprehensible to the audience. This seems
uncontentious.
Posting a straightforward change representing a relaxation of standards
(which were not in any case being enforced) should also be uncontentiou
do not necessarily require my opinions to be
thought reasonable, even by other reasonable people.
Kind regards,
Steve
On Mon, Jun 29, 2020 at 11:22 AM Nathaniel Smith wrote:
> On Mon, Jun 29, 2020 at 2:31 AM Steve Holden wrote:
> > The commit message used, however, reveals imple
Given that case will be a keyword, what's the case (pun unintentional) for
indenting the case clauses? What's wrong with 'case' and 'else' both
indented the same as match? Without the keyword there'd be a case for
indenting, but with it I don't see the necessity.
Kind regards,
Steve
On Fri, Jul
While I understand the point of view that says that match ... :
should encapsulate a sequence of indented suites, it seems to me that
match/case/case/.../else has a natural affinity with
try/except/except/.../finally/else, and nobody seems to think that the
excepts should be indented. Or the finall
Sadly micropython is not intended to support numerical libraries and other
such complex modules: the support for the Python standard library is pretty
much non-existent.
Kind regards,
Steve
On Wed, Jul 22, 2020 at 3:10 PM Huang, Yang wrote:
> Thank you for all your comments.
>
> I cannot agree
On Wed, Sep 16, 2020 at 3:53 PM Mark Shannon wrote:
> [...]
>
> maybe!(a.b)
>
> which would translate to:
>
> $tmp = a; None if $tmp is None else ($tmp.b)
>
> This reminds me very much of PL/1's "compile-time procedures," which
forty years ago were pretty much like PL/1 construct
Full marks to the SC for transparency. That's a healthy sign that the
community acknowledges its disciplinary processes must also be open to
scrutiny, and rather better than dealing with matters in a Star Council.
Kind regards,
Steve
On Fri, Oct 9, 2020 at 12:10 AM Thomas Wouters wrote:
>
> St
Since some code clearly accesses __version__, would it make sense to equip
all stdlib modules with a __version__ property that returned the Python
version, suitably prefixed?
Kind regards,
Steve
On Fri, Oct 16, 2020 at 5:28 AM Karthikeyan wrote:
> On Fri, Oct 16, 2020, 12:45 AM Serhiy Storchak
he same *could* be said about the existing
optimizations for objects that define their own __contains__.
regards
Steve
--
Steve Holden+1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
___
Python-Dev mailing l
Daniel Stutzbach wrote:
> On Tue, Feb 10, 2009 at 11:16 AM, Steve Holden <mailto:st...@holdenweb.com>> wrote:
>
> That's true, but the same *could* be said about the existing
> optimizations for objects that define their own __contains__.
>
&
ement was negative :)
So thanks to everyone who's taking the time to deal with this
low-profile not-very-glamorous issue. I, for one, appreciate it.
regards
Steve
--
Steve Holden+1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
___
Feb 17, 2009, David Russell wrote:
>> Dear Python Development Group,
>>
>> First of all sorry for the unsolicited email,
>
> This is spam, and you have now jeopardized your correct posting to the
> Python Job Board. The other website administrators will be informed and
Steve Holden wrote:
> David:
>
> Perhaps you'd like to give me your company's internal mailing list
> address so I can drop your staff a line when I hear of Python
> conferences going on your area. Or maybe that's not what the list is for?
>
[...]
Just to clos
mpatibility.
Fortunately I still had the SVN 1.4 client on the Ubuntu machine that
was hosting the Samba shares, so I could use ssh and the command line to
maintain things.
regards
Steve
--
Steve Holden+1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.c
Michael Foord wrote:
> Steve Holden wrote:
>> Steven Bethard wrote:
>>
>>> On Sat, Feb 21, 2009 at 1:11 PM, Paul Moore wrote:
>>>
>>>> PS Just for my own information, am I correct in thinking that it is
>>>> *only* Bazaar in the (D)VC
> $ ls -l w00t
> -rw-r- 1 guido eng 0 Feb 23 14:50 w00t
> $
>
>
> On Mon, Feb 23, 2009 at 2:41 PM, tav wrote:
>>> I take it back, we need to find all the trivial ones too.
>> Agreed!
>>
>>> BTW Tav, you ought to create a small website for this cha
has been proven to be
>> foolproof.
>
> Proven? Isn't it impossible to prove something like this? "Nobody ever
> see an alien" is not a proof for "There is no alien". "Nobody have
> thought of a way to break the model" is not a proof for "
utton on GUI.
>
> Could you please send the syntax for the same?
>
This list is for the development *of* Python. Your question would be
better addressed to comp.lang.python (python-list at python dot org).
There are many people on that list who will be able to help you.
regards
Steve
-
naming? I would think that "odict" or
> "ordereddict" would be more consistent with other collections names
> especially "defaultdict".
>
Surely that's just a thinko in the subject line? The PEP specifies
"ordered dictionary" and nobody has been ta
istent and the new ordered dict version would
>> go by
>> the name "OrderedDict".
>
> OK.
>
>> PS.: so is datetime.datetime a builtin then? :)
>
> Another historic accident. Like socket.socket. :-(
>
A pity this stuff wasn't addressed for 3.0. Way
the transition was being handled. In this case the old
> names and simply subclass the new names and have no issues with old code.
>
There's also no reason why someone couldn't write a pickle updater for
when such problems do rear their ugly heads.
regards
Steve
with pink polka dots, but I'm
> starting to appreciate why others are insisting on pink with green polka
> dots ;-)
>
This will be no surprise to those who have seen the many discussions on
ordered dicts that c.l.py has spawned over the years.
regards
Steve
--
Steve Holden+1 5
ather than *with*
Python, you should be OK. A couple of weeks lurking (or reading the list
history) will tell you most things you need to know.
regards
Steve
takes-all-sorts-to-make-a-world-ly y'rs - steve
--
Steve Holden+1 571 484 6266 +1 800 494 3119
Holden Web LLC
gt;
> Am still +1 on painting the class green with pink polka dots, but I'm
> starting to appreciate why others are insisting on pink with green polka
> dots ;-)
>
historydict?
regards
Steve
--
Steve Holden+1 571 484 6266 +1 800 494 3119
Holden Web LLC
ared earlier in this thread
>> and I missed it)?
>
> The same as always. We don't change APIs in bugfix releases.
>
Which unfortunately stops us from categorizing API breakages as bugs.
regards
Steve
--
Steve Holden+1 571 484 6266 +1 800 494 3119
Holden Web LLC
that someone could turn
> into a PEP relatively straightforwardly. Deal?
>
>
> Will any or all of you be at PyCon? I'd be willing to put in the extra
> work to turn your notes into a PEP.
>
OPEN SPACE!
--
Steve Holden+1 571 484 6
Jesse Noller wrote:
[...]I'll take it from anyone.
>
And we can *quote* you on that?
regards
Steve
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
Want to know? Come to PyCon - soon! http://us.p
are included.
>
Perhaps we could encourage more "jumbo" distributions, like Enthought's
and ActiveState's. I suspect many people would rather be able to
maintain their Python functionality as a single product.
regards
Steve
--
Steve Holden +1 571 484 6266 +1
any
> more of these!
Yes, well done, Benjamin. Barry Warsaw is walking with a spring in his
steps again ;-)
regards
Steve
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
Want to know? Come to
asked for help from Canonical
> with no reply.
> They seem reluctant to update Python beyond version 2.5; I'm trying to
> install 3.0.1.
> I'm a newb, and have tried rtfm--does someone have the incantation required?
> Thanks v. much in advance.
>
--
Steve
ther Python modules will give you a single analyzable module
tree. You don't even have to distribute the GUI if you don't want ...
So I don't see "jumbo" as replacing "batteries included". More like
"comes with 14v 300AH accumulator and support for domain name
from stdlib references.
Why not just put a section in both places that says "can't be bothered
to spell this out right now" and put a URL in referring to this thread
on Google ... that appears to have been the traditional approach to
import semantics :)
regards
Steve
--
Stev
a good
> mentor for it?
>
We also need projects for people who may want to do some coding and then
just walk away - the SoC experience might teach them that programming
isn't for them ;-)
regards
Steve
--
Steve Holden +1 571 484 6266 +1
contact
> info on the wiki so potential students can hash out the details with
> them before applying.
>
Realistically I am not sure I will have time to mentor, but if you need
any help from the PSF please feel free to get in touch. Thanks for
taking this challenging role up on behalf of
or coding is in-line. If you don't like the appearance of
> the output, the module is unusable. This is likely a two to
> three day project, easy and fun.
>
That makes it a much better candidate for GHOP that SoC, which requires
projects with a little more meat on them.
re
ent would be some enthusiasm from the
developer team for mobilizing such a potential source of assistance.
regards
Steve
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
Want to know? Come to PyCon - soon! http://us.pycon.org/
equirements and Python can't
satisfy them all without getting more complex.
Some people want an "all batteries and kitchen sink included" distro
that they can treat as a single component for configuration control
purposes. Others, like you, want the libraries to be separated out to
al
> superior alternative to".
>
> [2] If "your users" include Debian and RHEL users, you may find that
> they are not so happy with yet more PMS.
>
Seems to me that while all this is fine for developers and Python users
it's completely unsatisfactory for people who j
ystems independent of their distribution's packaging
standard. As time goes by, however, and the Lunix installed base
continues to grow, the majority of users will expect to rely on the
standard installation mechanisms of their distribution, and that will
never be setuptools or distutils.
regar
somewhat to
yield expr for x from X
The idea is that x should be a a bound variable in expr, but the "expr
for x" could be optional to yield the existing proposal as a degenerate
case.
> Also [...]
regards
Steve
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LL
"end users" won't wish to install individual Python modules
this argument may have had some merit, but I personally thought the
criticism unjustified since Mike's technique gave a uniform install
procedure for everything.
I don't think anyone was suggesting that py2exe woul
rson to request a
> "passing of judgement" from someone with more experience/authority? Post
> to python-dev? Given such a mechanism, I think I would be comfortable
> with the current workflow, with the expectation that I would need to
> call for assistance less and less freque
101 - 200 of 769 matches
Mail list logo
