named tuple mutability

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • castironpi@gmail.com

    named tuple mutability

    I'm concerned over the future of Python. Should tuples be named?
  • Raymond Hettinger

    #2
    Re: named tuple mutability

    > Should tuples be named?

    Yes.

    Comment

    • castironpi@gmail.com

      #3
      Re: named tuple mutability

      On May 14, 12:41 pm, Raymond Hettinger <pyt...@rcn.com wrote:
       Should tuples be named?
      >
      Yes.
      Not clearly should. Sequences ought be. If you're on the right time
      for both, can't the library hold the B?

      Comment

      • castironpi@gmail.com

        #4
        Re: named tuple mutability

        On May 14, 1:04 pm, castiro...@gmai l.com wrote:
        On May 14, 12:41 pm, Raymond Hettinger <pyt...@rcn.com wrote:
        >
        > Should tuples be named?
        >
        Yes.
        >
        Not clearly should.  Sequences ought be.  If you're on the right time
        for both, can't the library hold the B?
        On the web, you can. Both data types can go in the docs... sorry for
        the lunacy, I'm hacking.

        Comment

        • bruno.desthuilliers@gmail.com

          #5
          Re: named tuple mutability

          On 14 mai, 18:20, castiro...@gmai l.com wrote:
          I'm concerned over the future of Python. Should tuples be named?
          Obviously not, unless they should.

          Comment

          • Ben Finney

            #6
            Re: named tuple mutability

            "bruno.desthuil liers@gmail.com " <bruno.desthuil liers@gmail.com writes:
            On 14 mai, 18:20, castiro...@gmai l.com wrote:
            I'm concerned over the future of Python. Should tuples be named?
            >
            Obviously not, unless they should.
            Clearly they should, unless not.

            --
            \ “It is seldom that liberty of any kind is lost all at |
            `\ once.” —David Hume |
            _o__) |
            Ben Finney

            Comment

            • castironpi@gmail.com

              #7
              Re: named tuple mutability

              On May 14, 5:01 pm, Ben Finney <bignose+hate s-s...@benfinney. id.au>
              wrote:
              "bruno.desthuil li...@gmail.com " <bruno.desthuil li...@gmail.com writes:
              On 14 mai, 18:20, castiro...@gmai l.com wrote:
              I'm concerned over the future of Python.  Should tuples be named?
              >
              Obviously not, unless they should.
              >
              Clearly they should, unless not.
              >
              Ben Finney
              I have plenty of uses for them!

              Comment

              • castironpi@gmail.com

                #8
                Re: named tuple mutability

                On May 14, 5:28 pm, castiro...@gmai l.com wrote:
                On May 14, 5:01 pm, Ben Finney <bignose+hate s-s...@benfinney. id.au>
                wrote:
                >
                "bruno.desthuil li...@gmail.com " <bruno.desthuil li...@gmail.com writes:
                On 14 mai, 18:20, castiro...@gmai l.com wrote:
                I'm concerned over the future of Python.  Should tuples be named?
                >
                Obviously not, unless they should.
                >
                Clearly they should, unless not.
                >
                Ben Finney
                >
                I have plenty of uses for them!
                FOR INSTANCE!

                def zoop_zoop_zoop( self ): pass

                Comment

                • castironpi@gmail.com

                  #9
                  Re: named tuple mutability

                  On May 14, 12:41 pm, Raymond Hettinger <pyt...@rcn.com wrote:
                   Should tuples be named?
                  >
                  Yes.
                  Good; they're named sequences.

                  Comment

                  • castironpi@gmail.com

                    #10
                    Re: named tuple mutability

                    On May 14, 6:21 pm, castiro...@gmai l.com wrote:
                    On May 14, 12:41 pm, Raymond Hettinger <pyt...@rcn.com wrote:
                    >
                    > Should tuples be named?
                    >
                    Yes.
                    >
                    Good; they're named sequences.
                    Can anyone make sling-shots of words? What's the splatter?

                    Comment

                    • Bruno Desthuilliers

                      #11
                      Re: named tuple mutability

                      Ben Finney a écrit :
                      "bruno.desthuil liers@gmail.com " <bruno.desthuil liers@gmail.com writes:
                      >
                      >On 14 mai, 18:20, castiro...@gmai l.com wrote:
                      >>I'm concerned over the future of Python. Should tuples be named?
                      >Obviously not, unless they should.
                      >
                      Clearly they should, unless not.
                      >
                      May we agree to disagree here - unless we don't ?

                      Comment

                      • Ben Finney

                        #12
                        Re: named tuple mutability

                        Bruno Desthuilliers <bruno.42.desth uilliers@websit eburo.invalidwr ites:
                        May we agree to disagree here - unless we don't ?
                        Absolutely not, except where not applicable.

                        --
                        \ "I always wanted to be somebody. I see now that I should have |
                        `\ been more specific." -- Lily Tomlin |
                        _o__) |
                        Ben Finney

                        Comment

                        • Bruno Desthuilliers

                          #13
                          Re: named tuple mutability

                          Ben Finney a écrit :
                          Bruno Desthuilliers <bruno.42.desth uilliers@websit eburo.invalidwr ites:
                          >
                          >May we agree to disagree here - unless we don't ?
                          >
                          Absolutely not, except where not applicable.
                          >
                          and vice versa.

                          Comment

                          Working...