Create XML node with empty text content and with a named closing tag using ElementTree.SubElement












0















I can't seem to find a way to generate a sub-element like this



<child attr="something"></child>


Using the following code:



myChild = ElementTree.SubElement(root, tag="child", attrib={'attr': 'something'})



I always get:



<child attr="something" />


Unless I at least add:



whiteSpace = " "
myChild.text = whiteSpace


This is very annoying.



Is there a way that I can generate null text for the element with ElementTree?



UPDATES:



After some tries, I tend to agree that it really shouldn't matter. The reason why I asked is that I wanted to generate Xcode workspace file which uses empty content for it's project nodes. But I found that the default subElement actually works as well. So I won't put any more efforts in making the output XML in the "identical" format as the normal Xcode workspace.



Case closed.










share|improve this question




















  • 1





    why is it annoying? Its normal valid xml.

    – tdelaney
    Jul 3 '13 at 17:58
















0















I can't seem to find a way to generate a sub-element like this



<child attr="something"></child>


Using the following code:



myChild = ElementTree.SubElement(root, tag="child", attrib={'attr': 'something'})



I always get:



<child attr="something" />


Unless I at least add:



whiteSpace = " "
myChild.text = whiteSpace


This is very annoying.



Is there a way that I can generate null text for the element with ElementTree?



UPDATES:



After some tries, I tend to agree that it really shouldn't matter. The reason why I asked is that I wanted to generate Xcode workspace file which uses empty content for it's project nodes. But I found that the default subElement actually works as well. So I won't put any more efforts in making the output XML in the "identical" format as the normal Xcode workspace.



Case closed.










share|improve this question




















  • 1





    why is it annoying? Its normal valid xml.

    – tdelaney
    Jul 3 '13 at 17:58














0












0








0








I can't seem to find a way to generate a sub-element like this



<child attr="something"></child>


Using the following code:



myChild = ElementTree.SubElement(root, tag="child", attrib={'attr': 'something'})



I always get:



<child attr="something" />


Unless I at least add:



whiteSpace = " "
myChild.text = whiteSpace


This is very annoying.



Is there a way that I can generate null text for the element with ElementTree?



UPDATES:



After some tries, I tend to agree that it really shouldn't matter. The reason why I asked is that I wanted to generate Xcode workspace file which uses empty content for it's project nodes. But I found that the default subElement actually works as well. So I won't put any more efforts in making the output XML in the "identical" format as the normal Xcode workspace.



Case closed.










share|improve this question
















I can't seem to find a way to generate a sub-element like this



<child attr="something"></child>


Using the following code:



myChild = ElementTree.SubElement(root, tag="child", attrib={'attr': 'something'})



I always get:



<child attr="something" />


Unless I at least add:



whiteSpace = " "
myChild.text = whiteSpace


This is very annoying.



Is there a way that I can generate null text for the element with ElementTree?



UPDATES:



After some tries, I tend to agree that it really shouldn't matter. The reason why I asked is that I wanted to generate Xcode workspace file which uses empty content for it's project nodes. But I found that the default subElement actually works as well. So I won't put any more efforts in making the output XML in the "identical" format as the normal Xcode workspace.



Case closed.







python xml elementtree






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 4 '13 at 19:32







kakyo

















asked Jul 3 '13 at 15:01









kakyokakyo

2,56543562




2,56543562








  • 1





    why is it annoying? Its normal valid xml.

    – tdelaney
    Jul 3 '13 at 17:58














  • 1





    why is it annoying? Its normal valid xml.

    – tdelaney
    Jul 3 '13 at 17:58








1




1





why is it annoying? Its normal valid xml.

– tdelaney
Jul 3 '13 at 17:58





why is it annoying? Its normal valid xml.

– tdelaney
Jul 3 '13 at 17:58












1 Answer
1






active

oldest

votes


















1














The answer to the question is probably: There is no way to achieve what I wanted in the beginning.



But as the updates in my question said. The difference between the two mentioned formats really doesn't matter. They both work as valid XML.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17451473%2fcreate-xml-node-with-empty-text-content-and-with-a-named-closing-tag-using-eleme%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    The answer to the question is probably: There is no way to achieve what I wanted in the beginning.



    But as the updates in my question said. The difference between the two mentioned formats really doesn't matter. They both work as valid XML.






    share|improve this answer




























      1














      The answer to the question is probably: There is no way to achieve what I wanted in the beginning.



      But as the updates in my question said. The difference between the two mentioned formats really doesn't matter. They both work as valid XML.






      share|improve this answer


























        1












        1








        1







        The answer to the question is probably: There is no way to achieve what I wanted in the beginning.



        But as the updates in my question said. The difference between the two mentioned formats really doesn't matter. They both work as valid XML.






        share|improve this answer













        The answer to the question is probably: There is no way to achieve what I wanted in the beginning.



        But as the updates in my question said. The difference between the two mentioned formats really doesn't matter. They both work as valid XML.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jul 4 '13 at 19:34









        kakyokakyo

        2,56543562




        2,56543562
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17451473%2fcreate-xml-node-with-empty-text-content-and-with-a-named-closing-tag-using-eleme%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            MongoDB - Not Authorized To Execute Command

            How to fix TextFormField cause rebuild widget in Flutter

            Npm cannot find a required file even through it is in the searched directory