Re: DoesNotExist at /admin/blog/blog/add/: blog matching query does not exist

Sorry, the wrong list. Op 2022-09-12T20:35:46+ schreef mailingli...@vanwingerde.nl in bericht , inzake: het volgende. > Suddenly I can no longer add blogs to Django. Django says 'blog > matching query does not exist'. That seems strange to me because I > want to add

Re: DoesNotExist at /admin/blog/blog/add/: blog matching query does not exist

unsubscribe -Bat > On Sep 12, 2022, at 14:32, mailingli...@vanwingerde.nl wrote: > > Suddenly I can no longer add blogs to Django. Django says 'blog > matching query does not exist'. That seems strange to me because I want > to add something to the database and not request a b

DoesNotExist at /admin/blog/blog/add/: blog matching query does not exist

Suddenly I can no longer add blogs to Django. Django says 'blog matching query does not exist'. That seems strange to me because I want to add something to the database and not request a blog. What could be going on here? admin.py: class blogadmin(admin.ModelAdmin): def save_model(self

Zato blog post: A successful Python 3 migration story

The migration was from 2.7 to 2.7 and 3.x, rather than 3.x only. I think it worth reading for anyone interested in the subject. https://zato.io/blog/posts/python-3-migration-success-story.html 60,000 lines of Python and Cython, 130 external dependencies (but only 10 not already 3.x ready) took

Blog for basic python programming

Python for Engineers - Solve Problems by Coding Solutions https://pythonforengineers.blogspot.in -- https://mail.python.org/mailman/listinfo/python-list

Re: Beginners and experts (Batchelder blog post)

On Fri, Sep 29, 2017 at 12:14 PM, Bill wrote: > > I'll write for the possible benefit of any beginners who may be reading. > I guess by definition, if one still has a "bug" it's because one doesn't > quite understand what the code is doing. And I would say you should

Re: Beginners and experts (Batchelder blog post)

Bill wrote: Don't be afraid to write *really descriptive* output statements, and do so even though you "don't need to". Yeah, often when I'm writing something tricky I'll proactively put in some code to print intermediate state to reassure myself that things are on track. Being more verbose

Re: Beginners and experts (Batchelder blog post)

Steve D'Aprano wrote: (1) I know there's a bug in a specific chunk of code, but I'm having trouble working out where. When everything else fails, if I perturb the code a bit (reorder lines, calculate things in a different order, rename variables, etc) it may change the nature of the bug enough

Re: Beginners and experts (Batchelder blog post)

On Sat, Sep 30, 2017 at 5:14 AM, Bill wrote: > I'll write for the possible benefit of any beginners who may be reading. I > guess by definition, if one still has a "bug" it's because one doesn't quite > understand what the code is doing. And I would say you should lose

Re: Beginners and experts (Batchelder blog post)

On Sat, Sep 30, 2017 at 2:42 AM, Steve D'Aprano wrote: > Oh, and I'd like to make a (moderate) defense of a kind of "bug fixing by > random > perturbation". Obviously making unrelated, arbitrary changes to code is bad. > But making non-arbitrary but not fully

Re: Beginners and experts (Batchelder blog post)

On Fri, 29 Sep 2017 08:34 pm, D'Arcy Cain wrote: > On 09/29/2017 03:15 AM, Steve D'Aprano wrote: >> "Carefully-designed experiments" -- yeah, that is so totally how the coders >> I've worked with operate *wink* >> >> I think that's an awfully optimistic description of how the average >>

Re: Beginners and experts (Batchelder blog post)

On Fri, Sep 29, 2017 at 10:52 AM, justin walters wrote: > > I got through writing all of the above without realizing that you meant you > wanted to build a > desktop application and not a web application. Though, I think the advice > is still helpful. > > Yes and no.

Re: Beginners and experts (Batchelder blog post)

On Fri, Sep 29, 2017 at 2:57 AM, Leam Hall wrote: > On 09/27/2017 10:33 PM, Stefan Ram wrote: > >Some areas of knowledge follow, a programmer should not be >>ignorant in all of them: >> > > --- > > Stefan, this is list AWESOME! > > I have started mapping skills I have

Re: Beginners and experts (Batchelder blog post)

On Fri, Sep 29, 2017 at 8:34 PM, D'Arcy Cain wrote: > On 09/29/2017 03:15 AM, Steve D'Aprano wrote: >> >> "Carefully-designed experiments" -- yeah, that is so totally how the >> coders I've >> worked with operate *wink* >> >> I think that's an awfully optimistic

Re: Beginners and experts (Batchelder blog post)

On 09/29/2017 03:15 AM, Steve D'Aprano wrote: "Carefully-designed experiments" -- yeah, that is so totally how the coders I've worked with operate *wink* I think that's an awfully optimistic description of how the average programmer works :-) Better not hire average programmers then. I do

Re: Beginners and experts (Batchelder blog post)

Steve D'Aprano wrote: (say). Reading error messages is a skill that must be learned, even in Python. Let alone (say) gcc error messages, which are baroque to an extreme. The other day I was getting an error like: /tmp/ccchKJVU.o: In function `__static_initialization_and_destruction_0(int,

Re: Beginners and experts (Batchelder blog post)

On Fri, 29 Sep 2017 03:28 pm, Gregory Ewing wrote: > Chris Angelico wrote: >> finding the bug is basically searching >> through a problem space of all things that could potentially cause >> this symptom. A novice could accidentally stumble onto the right >> solution to a tricky bug, or an expert

Re: Beginners and experts (Batchelder blog post)

On Fri, Sep 29, 2017 at 3:28 PM, Gregory Ewing wrote: > Chris Angelico wrote: >> >> finding the bug is basically searching >> through a problem space of all things that could potentially cause >> this symptom. A novice could accidentally stumble onto the right >>

Re: Beginners and experts (Batchelder blog post)

Chris Angelico wrote: finding the bug is basically searching through a problem space of all things that could potentially cause this symptom. A novice could accidentally stumble onto the right solution to a tricky bug, or an expert could search a thousand other things and only get to the true

Re: Beginners and experts (Batchelder blog post)

On Thu, Sep 28, 2017 at 5:08 PM, Chris Angelico wrote: > Yep. Pick anyone on this list that you believe is an expert, and ask > him/her for a story of a long debug session that ended up finding a > tiny problem. I can pretty much guarantee that every expert programmer > will

Re: Beginners and experts (Batchelder blog post)

On Fri, Sep 29, 2017 at 7:47 AM, Bill wrote: > I won't claim to be any sort of "expert". But one memorable problem, for > me, was ultimately accounted for by the "inherent problem" of the floating > point variables x0 and xo coexisting in the same module. It's sort of

Re: Beginners and experts (Batchelder blog post)

Chris Angelico wrote: On Fri, Sep 29, 2017 at 6:59 AM, Bill wrote: Chris Angelico wrote: Be careful with this one. For anything other than trivial errors (and even for some trivial errors), finding the bug is basically searching through a problem space of all things

Re: Beginners and experts (Batchelder blog post)

On Fri, Sep 29, 2017 at 6:59 AM, Bill wrote: > Chris Angelico wrote: >> >> Be careful with this one. For anything other than trivial errors (and >> even for some trivial errors), finding the bug is basically searching >> through a problem space of all things that could

Re: Beginners and experts (Batchelder blog post)

Chris Angelico wrote: On Fri, Sep 29, 2017 at 5:45 AM, Bill wrote: Paul Moore wrote: On 27 September 2017 at 17:41, leam hall wrote: Hehe...I've been trying to figure out how to phrase a question. Knowing I'm not the only one who gets frustrated

Re: Beginners and experts (Batchelder blog post)

On Fri, Sep 29, 2017 at 5:45 AM, Bill wrote: > Paul Moore wrote: >> >> On 27 September 2017 at 17:41, leam hall wrote: >>> >>> Hehe...I've been trying to figure out how to phrase a question. Knowing >>> I'm >>> not the only one who gets frustrated

Re: Beginners and experts (Batchelder blog post)

Paul Moore wrote: On 27 September 2017 at 17:41, leam hall wrote: Hehe...I've been trying to figure out how to phrase a question. Knowing I'm not the only one who gets frustrated really helps. I'm trying to learn to be a programmer. I can look at a book and read basic code

Re: Beginners and experts (Batchelder blog post)

On 09/28/2017 04:15 AM, Paul Moore wrote: With Python, I'd say that an appreciation of the available libraries is key - both what's in the stdlib, and what's available from PyPI. That's not to say you should memorise the standard library, but rather cultivate an approach of "hmm, I'm pretty sure

Re: Beginners and experts (Batchelder blog post)

On 09/28/2017 07:35 AM, Stefan Ram wrote: But remember that paid programmers usually do not "code", in the sense of "write a program from scratch". Most of the work is maintenance programming, where an important part of the job is to read and understand a piece of code. Coding

Re: Beginners and experts (Batchelder blog post)

My question has received several helpful responses, thanks! On 09/28/2017 01:01 PM, Dennis Lee Bieber wrote: On Wed, 27 Sep 2017 12:41:24 -0400, leam hall declaimed the following: "Programmer"... or "Software Engineer"? I haven't kept up on "job titles" but

Re: Beginners and experts (Batchelder blog post)

On 2017-09-28, bartc wrote: > On 28/09/2017 12:31, Steve D'Aprano wrote: >> Until now, I thought that people who wrote crappy code did so >> because they didn't know any better. This is the first time >> I've seen somebody state publicly that they have no interest >> in writing

Re: Beginners and experts (Batchelder blog post)

On 28/09/2017 12:31, Steve D'Aprano wrote: On Thu, 28 Sep 2017 09:12 pm, bartc wrote: And I have little interest in most of this lot (my eyes glaze over just reading some of these): > - how to use operating systems You've never used a system call? Written to a file? Moved the mouse?

Re: Beginners and experts (Batchelder blog post)

On Wed, 27 Sep 2017 18:18:10 -0700, Larry Hudson wrote: > On 09/27/2017 09:41 AM, leam hall wrote: >> On Sat, Sep 23, 2017 at 5:26 PM, Ned Batchelder >> wrote: > [snip] >> >> The question is, what should a person "know" when hiring out as a >> programmer? What is 'know"

Re: Beginners and experts (Batchelder blog post)

On Thu, 28 Sep 2017 09:12 pm, bartc wrote: > And I have little interest in most of this lot (my eyes glaze over just > reading some of these): > > > - how to use operating systems You've never used a system call? Written to a file? Moved the mouse? > > - how to use an editor well

Re: Beginners and experts (Batchelder blog post)

On 28/09/2017 03:33, Stefan Ram wrote: Larry Hudson writes: Hopefully NOT like this person... Since I teach nights at a local community college a programmer who couldn't program It is not clear what »this person« refers to: Do you hope one is not like that

Re: Beginners and experts (Batchelder blog post)

On 27 September 2017 at 17:41, leam hall wrote: > Hehe...I've been trying to figure out how to phrase a question. Knowing I'm > not the only one who gets frustrated really helps. > > I'm trying to learn to be a programmer. I can look at a book and read basic > code in a few

Re: Beginners and experts (Batchelder blog post)

On Wed, 27 Sep 2017 12:41:24 -0400, leam hall wrote: > The question is, what should a person "know" when hiring out as a > programmer? What is 'know" and what should be "known"? Specifically > with Python. The longer I claim to be a programmer, the more I discover how wide a net that is. Web

Re: Beginners and experts (Batchelder blog post)

On Thu, Sep 28, 2017 at 11:18 AM, Larry Hudson via Python-list wrote: > > It had turned out his company had paid for him to take the course. Since he > failed, it suddenly came to the attention of his employer that he didn't > know how to program, and now his job was in

Re: Beginners and experts (Batchelder blog post)

On 09/27/2017 09:41 AM, leam hall wrote: On Sat, Sep 23, 2017 at 5:26 PM, Ned Batchelder wrote: [snip] The question is, what should a person "know" when hiring out as a programmer? What is 'know" and what should be "known"? Specifically with Python. Hopefully NOT

Re: Beginners and experts (Batchelder blog post)

On Wed, Sep 27, 2017 at 12:41 PM, leam hall wrote: > The question is, what should a person "know" when hiring out as a > programmer? What is 'know" and what should be "known"? Specifically with > Python. Fake it till you make it! --

Re: Beginners and experts (Batchelder blog post)

On Sat, Sep 23, 2017 at 5:26 PM, Ned Batchelder <n...@nedbatchelder.com> wrote: > On 9/23/17 2:52 PM, Leam Hall wrote: > >> On 09/23/2017 02:40 PM, Terry Reedy wrote: >> >>> https://nedbatchelder.com//blog/201709/beginners_and_experts.html >>> >>>

Re: Beginners and experts (Batchelder blog post)

On 9/23/17 2:52 PM, Leam Hall wrote: On 09/23/2017 02:40 PM, Terry Reedy wrote: https://nedbatchelder.com//blog/201709/beginners_and_experts.html Great post. Yup. Thanks for the link. I often have that "I bet Fred> doesn't get frustrated." thing going. Nice to know Ned bangs

Re: Beginners and experts (Batchelder blog post)

On 9/23/2017 2:52 PM, Leam Hall wrote: On 09/23/2017 02:40 PM, Terry Reedy wrote: https://nedbatchelder.com//blog/201709/beginners_and_experts.html Great post. Yup. Thanks for the link. I often have that "I bet Fred> doesn't get frustrated." thing going. Nice to know Ned bangs

Re: Beginners and experts (Batchelder blog post)

On 09/23/2017 02:40 PM, Terry Reedy wrote: https://nedbatchelder.com//blog/201709/beginners_and_experts.html Great post. Yup. Thanks for the link. I often have that "I bet Fred> doesn't get frustrated." thing going. Nice to know Ned bangs his head now and again. :P Le

Beginners and experts (Batchelder blog post)

https://nedbatchelder.com//blog/201709/beginners_and_experts.html Great post. -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list

Re: Planet Scipy blog

On 08/10/2015 14:39, beliavsky--- via Python-list wrote: There used to be a blog about SciPy at https://planet.scipy.org/ , discussing the applications of Python to scientific computing. Now there is a static page about "MPI for Python". What happened? Presumably http://www

Re: Planet Scipy blog

In a message of Thu, 08 Oct 2015 15:10:21 +0100, Mark Lawrence writes: >On 08/10/2015 14:39, beliavsky--- via Python-list wrote: >> There used to be a blog about SciPy at https://planet.scipy.org/ , >> discussing the applications of Python to scientific computing. Now there is &

Planet Scipy blog

There used to be a blog about SciPy at https://planet.scipy.org/ , discussing the applications of Python to scientific computing. Now there is a static page about "MPI for Python". What happened? -- https://mail.python.org/mailman/listinfo/python-list

Re: Planet Scipy blog

On Thu, 8 Oct 2015 15:29 Laura Creighton <l...@openend.se> wrote: In a message of Thu, 08 Oct 2015 15:10:21 +0100, Mark Lawrence writes: >On 08/10/2015 14:39, beliavsky--- via Python-list wrote: >> There used to be a blog about SciPy at https <https://planet.scip

EuroPython has a new blog

The EuroPython Society has setup a new blog for EuroPython in its efforts to provide more conference facilities for the EuroPython organization and to enhance the EuroPython attendee experience. http://blog.europython.eu/ There’s an RSS feed in case you want to subscribe to it: http

EuroPython has a new blog

The EuroPython Society has setup a new blog for EuroPython in its efforts to provide more conference facilities for the EuroPython organization and to enhance the EuroPython attendee experience. http://blog.europython.eu/ There’s an RSS feed in case you want to subscribe to it: http

Re: EuroPython has a new blog

Hi Marc-André, Cool for EuroPython, Good idea, I think we will use tumblr for a small blog for Python-FOSDEM. Stef On 17 Jan 2014, at 13:37, M.-A. Lemburg wrote: The EuroPython Society has setup a new blog for EuroPython in its efforts to provide more conference facilities

Re: Blog about python 3

Le mercredi 8 janvier 2014 01:02:22 UTC+1, Terry Reedy a écrit : On 1/7/2014 9:54 AM, Terry Reedy wrote: On 1/7/2014 8:34 AM, wxjmfa...@gmail.com wrote: Le dimanche 5 janvier 2014 23:14:07 UTC+1, Terry Reedy a écrit : Memory: Point 2. A *design goal* of FSR was to save memory

Re: Blog about python 3

On 1/8/2014 4:59 AM, wxjmfa...@gmail.com wrote: [responding to me] The FSR acts more as an coding scheme selector That is what PEP 393 describes and what I and many others have said. The FSR saves memory by selecting from three choices the most compact coding scheme for each string. I ask

Re: Blog about python 3

On 07/01/2014 13:34, wxjmfa...@gmail.com wrote: Le dimanche 5 janvier 2014 23:14:07 UTC+1, Terry Reedy a écrit : Ned : this has already been explained and illustrated. jmf This has never been explained and illustrated. Roughly 30 minutes ago Terry Reedy once again completely shot your

Re: Blog about python 3

Le dimanche 5 janvier 2014 23:14:07 UTC+1, Terry Reedy a écrit : On 1/5/2014 9:23 AM, wxjmfa...@gmail.com wrote: Le samedi 4 janvier 2014 23:46:49 UTC+1, Terry Reedy a écrit : On 1/4/2014 2:10 PM, wxjmfa...@gmail.com wrote: And I could add, I *never* saw once one soul, who is

Re: Blog about python 3

On 1/7/2014 8:34 AM, wxjmfa...@gmail.com wrote: Le dimanche 5 janvier 2014 23:14:07 UTC+1, Terry Reedy a écrit : Memory: Point 2. A *design goal* of FSR was to save memory relative to UTF-32, which is what you apparently prefer. Your examples show that FSF successfully met its design goal.

Re: Blog about python 3

On 8 January 2014 00:34, wxjmfa...@gmail.com wrote: Point 2: This Flexible String Representation does no effectuate any memory optimization. It only succeeds to do the opposite of what a corrrect usage of utf* do. UTF-8 is a variable-width encoding that uses less memory to encode code

Re: Blog about python 3

On 1/7/2014 9:54 AM, Terry Reedy wrote: On 1/7/2014 8:34 AM, wxjmfa...@gmail.com wrote: Le dimanche 5 janvier 2014 23:14:07 UTC+1, Terry Reedy a écrit : Memory: Point 2. A *design goal* of FSR was to save memory relative to UTF-32, which is what you apparently prefer. Your examples show

Re: Blog about python 3

On Sat, Jan 4, 2014 at 6:27 PM, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: Fast is never more important than correct. It's just that sometimes you might compromise a little (or a lot) on what counts as correct in order for some speed. Is this statement even falsifiable? Can

Re: Blog about python 3

Le dimanche 5 janvier 2014 03:54:29 UTC+1, Chris Angelico a écrit : On Sun, Jan 5, 2014 at 1:41 PM, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: wxjmfa...@gmail.com wrote: The very interesting aspect in the way you are holding unicodes (strings). By comparing

Re: Blog about python 3

On 31.12.2013 10:53, Steven D'Aprano wrote: Mark Lawrence wrote: http://blog.startifact.com/posts/alex-gaynor-on-python-3.html. I quote: ...perhaps a brave group of volunteers will stand up and fork Python 2, and take the incremental steps forward. This will have to remain just an idle

Re: Blog about python 3

Devin Jeanpierre wrote: On Sat, Jan 4, 2014 at 6:27 PM, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: Fast is never more important than correct. It's just that sometimes you might compromise a little (or a lot) on what counts as correct in order for some speed. Is this

Re: Blog about python 3

On Sun, Jan 5, 2014 at 11:28 PM, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: - The Unix 'locate' command doesn't do a live search of the file system because that would be too slow, it uses a snapshot of the state of the file system. Is locate buggy because it tells you

Re: Blog about python 3

On 31/12/2013 09:53, Steven D'Aprano wrote: Mark Lawrence wrote: http://blog.startifact.com/posts/alex-gaynor-on-python-3.html. I quote: ...perhaps a brave group of volunteers will stand up and fork Python 2, and take the incremental steps forward. This will have to remain just an idle

Re: Blog about python 3

Johannes Bauer, 05.01.2014 13:14: I've pushed the migration of *large* projects at work to Python3 when support was pretty early and it really wasn't a huge deal. I think there are two sides to consider. Those who can switch their code base to Py3 and be happy (as you did, apparently), and

Re: Blog about python 3

Le samedi 4 janvier 2014 23:46:49 UTC+1, Terry Reedy a écrit : On 1/4/2014 2:10 PM, wxjmfa...@gmail.com wrote: Le samedi 4 janvier 2014 15:17:40 UTC+1, Chris Angelico a écrit : any, and Python has only one, idiot like jmf who completely Chris, I appreciate the many

Re: Blog about python 3

On 1/5/14 9:23 AM, wxjmfa...@gmail.com wrote: Le samedi 4 janvier 2014 23:46:49 UTC+1, Terry Reedy a écrit : On 1/4/2014 2:10 PM, wxjmfa...@gmail.com wrote: I do not mind to be considered as an idiot, but I'm definitively not blind. And I could add, I *never* saw once one soul, who is

Re: Blog about python 3

In article 52c94fec$0$29973$c3e8da3$54964...@news.astraweb.com, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: How do we tell when software is buggy? We compare what it actually does to the promised behaviour, or expected behaviour, and if there is a discrepancy, we call it a

Re: Blog about python 3

In article mailman.4930.1388908293.18130.python-l...@python.org, Chris Angelico ros...@gmail.com wrote: On Sun, Jan 5, 2014 at 2:20 PM, Roy Smith r...@panix.com wrote: I've got a new sorting algorithm which is guaranteed to cut 10 seconds off the sorting time (i.e. $0.10 per package). The

Re: Blog about python 3

On Mon, Jan 6, 2014 at 3:34 AM, Roy Smith r...@panix.com wrote: Amazon's (short-term) goal is to increase their market share by undercutting everybody on price. They have implemented a box-packing algorithm which clearly has a bug in it. You are complaining that they failed to deliver your

Re: Blog about python 3

Chris Angelico ros...@gmail.com wrote: Can you really run a business by not caring about your customers? http://snltranscripts.jt.org/76/76aphonecompany.phtml -- https://mail.python.org/mailman/listinfo/python-list

Re: Blog about python 3

On 1/5/2014 9:23 AM, wxjmfa...@gmail.com wrote: Le samedi 4 janvier 2014 23:46:49 UTC+1, Terry Reedy a écrit : On 1/4/2014 2:10 PM, wxjmfa...@gmail.com wrote: And I could add, I *never* saw once one soul, who is explaining what I'm doing wrong in the gazillion of examples I gave on this list.

Re: Blog about python 3

On 1/5/2014 9:23 AM, wxjmfa...@gmail.com wrote: My examples are ONLY ILLUSTRATING, this FSR is wrong by design, Let me answer you a different way. If FSR is 'wrong by design', so are the alternatives. Hence, the claim is, in itself, useless as a guide to choosing. The choices: * Keep the

Re: Blog about python 3

On 1/5/2014 11:51 AM, Chris Angelico wrote: On Mon, Jan 6, 2014 at 3:34 AM, Roy Smith r...@panix.com wrote: Amazon's (short-term) goal is to increase their market share by undercutting everybody on price. They have implemented a box-packing algorithm which clearly has a bug in it. You are

Re: Blog about python 3

On Mon, Jan 6, 2014 at 9:56 AM, Terry Reedy tjre...@udel.edu wrote: On 1/5/2014 11:51 AM, Chris Angelico wrote: On Mon, Jan 6, 2014 at 3:34 AM, Roy Smith r...@panix.com wrote: Amazon's (short-term) goal is to increase their market share by undercutting everybody on price. They have

Re: Blog about python 3

Chris Angelico wrote about Amazon: And yet I can't disagree with your final conclusion. Empirical evidence goes against my incredulous declaration that surely this is a bad idea - according to XKCD 1165, they're kicking out nearly a cubic meter a SECOND of packages. Yes, but judging by

Re: Blog about python 3

Roy Smith wrote: In article mailman.4930.1388908293.18130.python-l...@python.org, Chris Angelico ros...@gmail.com wrote: On Sun, Jan 5, 2014 at 2:20 PM, Roy Smith r...@panix.com wrote: I've got a new sorting algorithm which is guaranteed to cut 10 seconds off the sorting time (i.e.

Re: Blog about python 3

On Mon, Jan 6, 2014 at 12:23 PM, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: (However, to the extent that Amazon has gained monopoly power over the book market, that reasoning may not apply. Amazon is not *technically* a monopoly, but they are clearly well on the way to becoming

Re: Blog about python 3

On 06/01/2014 01:54, Chris Angelico wrote: On Mon, Jan 6, 2014 at 12:23 PM, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: (However, to the extent that Amazon has gained monopoly power over the book market, that reasoning may not apply. Amazon is not *technically* a monopoly, but

Re: Blog about python 3

Le vendredi 3 janvier 2014 12:14:41 UTC+1, Robin Becker a écrit : On 02/01/2014 18:37, Terry Reedy wrote: On 1/2/2014 12:36 PM, Robin Becker wrote: I just spent a large amount of effort porting reportlab to a version which works with both python2.7 and python3.3. I have a large

Re: Blog about python 3

In article mailman.4882.1388808283.18130.python-l...@python.org, Mark Lawrence breamore...@yahoo.co.uk wrote: Surely everybody prefers fast but incorrect code in preference to something that is correct but slow? I realize I'm taking this statement out of context, but yes, sometimes fast is

Re: Blog about python 3

On Sun, Jan 5, 2014 at 12:55 AM, Roy Smith r...@panix.com wrote: In article mailman.4882.1388808283.18130.python-l...@python.org, Mark Lawrence breamore...@yahoo.co.uk wrote: Surely everybody prefers fast but incorrect code in preference to something that is correct but slow? I realize I'm

Re: Blog about python 3

On 1/4/14 9:17 AM, Chris Angelico wrote: On Sun, Jan 5, 2014 at 12:55 AM, Roy Smith r...@panix.com wrote: In article mailman.4882.1388808283.18130.python-l...@python.org, Mark Lawrence breamore...@yahoo.co.uk wrote: Surely everybody prefers fast but incorrect code in preference to something

Re: Blog about python 3

Le samedi 4 janvier 2014 15:17:40 UTC+1, Chris Angelico a écrit : On Sun, Jan 5, 2014 at 12:55 AM, Roy Smith r...@panix.com wrote: In article mailman.4882.1388808283.18130.python-l...@python.org, Mark Lawrence breamore...@yahoo.co.uk wrote: Surely everybody prefers fast but

Re: Blog about python 3

On 1/4/2014 2:10 PM, wxjmfa...@gmail.com wrote: Le samedi 4 janvier 2014 15:17:40 UTC+1, Chris Angelico a écrit : any, and Python has only one, idiot like jmf who completely Chris, I appreciate the many contributions you make to this list, but that does not exempt you from out standard of

Re: Blog about python 3

On Sun, Jan 5, 2014 at 9:46 AM, Terry Reedy tjre...@udel.edu wrote: On 1/4/2014 2:10 PM, wxjmfa...@gmail.com wrote: Le samedi 4 janvier 2014 15:17:40 UTC+1, Chris Angelico a écrit : any, and Python has only one, idiot like jmf who completely Chris, I appreciate the many contributions you

Re: Blog about python 3

Roy Smith wrote: In article mailman.4882.1388808283.18130.python-l...@python.org, Mark Lawrence breamore...@yahoo.co.uk wrote: Surely everybody prefers fast but incorrect code in preference to something that is correct but slow? I realize I'm taking this statement out of context, but

Re: Blog about python 3

On Sun, Jan 5, 2014 at 1:27 PM, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: But regardless of how fast your path-finder algorithm might become, you're unlikely to be satisfied with a solution that travels around in a circle from A to B a million times then shoots off straight to

Re: Blog about python 3

On 2014-01-05 02:32, Chris Angelico wrote: On Sun, Jan 5, 2014 at 1:27 PM, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: But regardless of how fast your path-finder algorithm might become, you're unlikely to be satisfied with a solution that travels around in a circle from A to B

Re: Blog about python 3

wxjmfa...@gmail.com wrote: The very interesting aspect in the way you are holding unicodes (strings). By comparing Python 2 with Python 3.3, you are comparing utf-8 with the the internal representation of Python 3.3 (the flexible string represenation). This is incorrect. Python 2 has never

Re: Blog about python 3

On Sun, Jan 5, 2014 at 1:41 PM, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: wxjmfa...@gmail.com wrote: The very interesting aspect in the way you are holding unicodes (strings). By comparing Python 2 with Python 3.3, you are comparing utf-8 with the the internal representation

Re: Blog about python 3

I wrote: I realize I'm taking this statement out of context, but yes, sometimes fast is more important than correct. In article 52c8c301$0$29998$c3e8da3$54964...@news.astraweb.com, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: Fast is never more important than correct. Sure

Re: Blog about python 3

On Sun, Jan 5, 2014 at 8:50 AM, Roy Smith r...@panix.com wrote: I wrote: I realize I'm taking this statement out of context, but yes, sometimes fast is more important than correct. In article 52c8c301$0$29998$c3e8da3$54964...@news.astraweb.com, Steven D'Aprano

Re: Blog about python 3

In article mailman.4929.1388896998.18130.python-l...@python.org, Rustom Mody rustompm...@gmail.com wrote: On Sun, Jan 5, 2014 at 8:50 AM, Roy Smith r...@panix.com wrote: I wrote: I realize I'm taking this statement out of context, but yes, sometimes fast is more important than correct.

Re: Blog about python 3

Roy Smith wrote: I wrote: I realize I'm taking this statement out of context, but yes, sometimes fast is more important than correct. In article 52c8c301$0$29998$c3e8da3$54964...@news.astraweb.com, Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote: Fast is never more important

Re: Blog about python 3

On Sun, Jan 5, 2014 at 2:20 PM, Roy Smith r...@panix.com wrote: I've got a new sorting algorithm which is guaranteed to cut 10 seconds off the sorting time (i.e. $0.10 per package). The problem is, it makes a mistake 1% of the time. That's a valid line of argument in big business, these days,

Re: Blog about python 3

On 1/2/2014 11:49 PM, Steven D'Aprano wrote: Robin Becker wrote: For fairly sensible reasons we changed the internal default to use unicode rather than bytes. After doing all that and making the tests compatible etc etc I have a version which runs in both and passes all its tests. However, for

Re: Blog about python 3

It's time to understand the Character Encoding Models and the math behind it. Unicode does not differ from any other coding scheme. How? With a sheet of paper and a pencil. jmf -- https://mail.python.org/mailman/listinfo/python-list

Re: Blog about python 3

On Fri, Jan 3, 2014 at 9:10 PM, wxjmfa...@gmail.com wrote: It's time to understand the Character Encoding Models and the math behind it. Unicode does not differ from any other coding scheme. How? With a sheet of paper and a pencil. One plus one is two, therefore Python is better than

Re: Blog about python 3

On 02/01/2014 18:25, David Hutto wrote: Just because it's 3.3 doesn't matter...the main interest is in compatibility. Secondly, you used just one piece of code, which could be a fluke, try others, and check the PEP. You need to realize that evebn the older versions are benig worked on, and they

  1   2   3   4   5   6   >