<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    On point #1:<br>
    Yes, both package management and the unmanaged exports package work
    correctly on linux under MD.<br>
    <br>
    <div class="moz-cite-prefix">On 11/27/2013 1:38 AM, Kyle Rocha
      wrote:<br>
    </div>
    <blockquote
cite="mid:CACObT9zhgiU-+LpURT4MQJqY+nLAa3hOsY__PWbM41jRspDEUw@mail.gmail.com"
      type="cite">
      <p dir="ltr">I would like to continue to see proper mono support
        available.</p>
      <p dir="ltr">That does lead me to some questions about that
        unmanaged exports package.<br>
        1. Does that stuff work correctly when you're using something
        like monodevelop?</p>
      <p dir="ltr">2. Why was the change made to use that over the
        manually written clr bindings? Was it only to simplify the
        binding process?</p>
      <p dir="ltr">/ Kyle </p>
      <div class="gmail_quote">On Nov 26, 2013 9:18 AM, "davidacoder"
        <<a moz-do-not-send="true"
          href="mailto:davidacoder@hotmail.com">davidacoder@hotmail.com</a>>
        wrote:<br type="attribution">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div link="#0563C1" vlink="#954F72" lang="EN-US">
            <div>
              <p class="MsoNormal">Hi,</p>
              <p class="MsoNormal"> </p>
              <p class="MsoNormal">I think one major barrier for easier
                adoption of pythondotnet right now is setup, i.e. how
                you get to a point where you can just use it.</p>
              <p class="MsoNormal"> </p>
              <p class="MsoNormal">I think there are a couple of issues:</p>
              <p class="MsoNormal"> </p>
              <p class="MsoNormal">- the download page on sourceforge is
                confusing. There are five folders on the first page that
                don’t seem to follow some common naming scheme. Three
                have a pythonnet version in it, one doesn’t have any
                version in the name and the last one refers to a CLR
                version. If I land there I just don’t know what to do
                next.</p>
              <p class="MsoNormal">- There doesn’t seem to be a win x64
                download, which I would assume to be the major version
                in use right now.</p>
              <p class="MsoNormal">- In general the builds seem to be
                old</p>
              <p class="MsoNormal">- There don’t seem to be mono builds
                (although, should there be?)</p>
              <p class="MsoNormal"> </p>
              <p class="MsoNormal">At the same time I feel that with the
                new package stuff happening in the general python world
                the idea of having a binary zip file download is getting
                old in any case.</p>
              <p class="MsoNormal"> </p>
              <p class="MsoNormal">One potentially elegant way around
                this is to provide binary wheels for pythondotnet that
                are hosted on <a moz-do-not-send="true"
                  href="http://pypi.python.org" target="_blank">pypi.python.org</a>
                for windows. I don’t know how the mono stuff would work
                and multi-platform things, though… In any case, I think
                it should be feasible at that point to simply use pip to
                install pythondotnet:</p>
              <p class="MsoNormal"> </p>
              <p class="MsoNormal">pip install pythondotnet</p>
              <p class="MsoNormal"> </p>
              <p class="MsoNormal">and that would do the trick. And now
                that pip is bundled in the default python distribution,
                I feel that would essentially solve the distribution
                problem completely, right? I think such a pip install
                should just make the clr module available for import. I
                am less sure whether such a wheel install should also
                put npython.exe somewhere onto the path (scripts
                folder?).</p>
              <p class="MsoNormal"> </p>
              <p class="MsoNormal">Thoughts?</p>
              <p class="MsoNormal"> </p>
              <p class="MsoNormal">Thanks,</p>
              <p class="MsoNormal">David</p>
              <p class="MsoNormal">
                 </p>
              <p class="MsoNormal"> </p>
            </div>
          </div>
          <br>
          _________________________________________________<br>
          Python.NET mailing list - <a moz-do-not-send="true"
            href="mailto:PythonDotNet@python.org">PythonDotNet@python.org</a><br>
          <a moz-do-not-send="true"
            href="https://mail.python.org/mailman/listinfo/pythondotnet"
            target="_blank">https://mail.python.org/mailman/listinfo/pythondotnet</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_________________________________________________
Python.NET mailing list - <a class="moz-txt-link-abbreviated" href="mailto:PythonDotNet@python.org">PythonDotNet@python.org</a>
<a class="moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/pythondotnet">https://mail.python.org/mailman/listinfo/pythondotnet</a></pre>
    </blockquote>
    <br>
  </body>
</html>