Re: [Distutils] Call for information - What assumptions can I make about Unix users' access to Windows?
Regarding remote access to windows machines, there are several options: - Remote powershell (not my area, so not sure how viable this is) - Use pexec from sysinternals to run cmd.exe remotely (probably on local network only, and only from other windows machines, so probably not that helpful) - Windows comes with a telnet server (obviously not very secure, but you could use stunnel/vpn or similar to help here) - WinRM (and pywinrm as has been mentioned). Note that vagrant either does or will soon support talking to Windows VMs using this method. - SSH: it is possible to set up an ssh server to work on Windows, but is...non-trivial (i.e. hard) and many caveats apply. See freesshd or KpyM. There are also some GUI options: - RDP - the venerable VNC Obvioiusly the GUI options are more difficult to automate. On Sun, Nov 9, 2014 at 6:28 AM, Paul Moore wrote: > On 9 November 2014 12:21, Tim Golden wrote: > > I think the OP was speaking not so much about having the technical > > wherewithal to use RDP but rather about the experience of RDP vs SSH. > > That was certainly my understanding. The key issue for me is to try to > make the process of just running "pip wheel myproject" or "pip wheel > git+https://github.com/me/myproject"; as simple and painless as > possible for people without Windows experience. > > That's somewhat optimistic, because if the command fails with an > error, the developer is still going to need to work out how to debug > why the code isn't portable, etc. But that's a whole different > situation, and well out of scope. > > > The > > difficulty is that Windows doesn't really "think" in ssh. I believe there > > are (third-party) mechanisms to provide ssh-like access, but I don't know > > how successful they really are. > > Yeah, that's where things like cygwin probably won't work well, > because you don't get the "normal" Windows environment. But it might > be possible - after all, see above - it's really only a few simple > commands we need to support. > > Paul > ___ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig > -- -- Kevin Horn ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Beyond wheels 1.0: helping downstream, FHS and more
On Tue, Apr 14, 2015 at 4:19 PM, Paul Moore wrote: > On 14 April 2015 at 22:02, Chris Barker wrote: > > Personally, I'm not a fan of auto-installing, so I'd hope for > something more like pip would fail to install if a required extension > were missing. The user would then install the extension and redo the > install. But that may be a minority opinion - it's a bit like > setup_requires in principle, and people seem to prefer that to be > auto-installed. > > (lurker surfaces) I'm with Paul on this one. It seems to me that auto-installing the extension would destroy most of the advantages of distributing the extensions separately. I _might_ not hate it if pip prompted the user and _then_ installed, but then again, I might. (lurker sinks back into the depths) -- Kevin Horn ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] pywin32 on wheels [was: Beyond wheels 1.0: helping downstream, FHS and more]
#x27;ve no
> > idea why this is necessary, or precisely which parts of pywin32
> > require it (I've a recollection from a long time ago that "services
> > written in Python" was the explanation, but that's all I know). But
> > presumably such use cases already break with a per-user Python
> > install?
> > 3. Registering the ActiveX COM DLLs. I believe this is mostly obsolete
> > technology these days (who still uses ActiveX Scripting in anything
> > other than VBScript or maybe a bit of JScript?) I'd drop this and make
> > it a step that the user has to do manually if they want it. In place
> > of it, pywin32 could provide an entry point to register the DLLs
> > ("python -m pywin32 --register-dlls" or something). Presumably users
> > who need it would understand the implications, and how to avoid
> > registering multiple environments or forgetting to unregister before
> > dropping an environment, etc. That sort of pitfall isn't something
> > Python should try to solve automatically via pre- and post- install
> > scripts.
> > 4. Registering help files. I never understood how that worked or why
> > it was needed. So again, I'd say just drop it.
>
> Really, pywin32 is several things: a set of libraries (win32api,
> win32file, etc.); some system-level support for various things (COM
> registration, Service support etc.); and a development/editing
> environment (pythonwin).
>
> I see this ending up as (respectively): as venv-friendly wheel; a py -m
> script of the kind Paul suggests; and an installable app with the usual
> start menu icons etc.
>
> In my copious spare time I'll at least try to visit the pywin32 codebase
> to see how viable all this is. Feel free to challenge my thoughts on the
> matter.
>
>
> TJG
>
> ___
> Distutils-SIG maillist - Distutils-SIG@python.org
> https://mail.python.org/mailman/listinfo/distutils-sig
>
--
--
Kevin Horn
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] python-meta-packaging resource hub
Howdy! I've been lurking on the list for a while, but have been pretty quiet so far. I was watching the live stream of the PyCon packaging panel today and the pytjon-meta-packaging resource hub idea was mentioned, which I hadn't heard of before, and was spurred to action. So I created a skeleton Sphinx project in a fork of this project here: https://bitbucket.org/khorn/python-meta-packaging Sadly, bitbucket won't let me do a pull request for some reason. If anyone knows why that is, feel free to let me know. (FYI I think it's because the main repo has no commits in it, which makes the "Create a pull request not load properly.) At any rate, somebody somewhere should feel free pull it into the main repo, so we can get things moving on that front. I'm happy to help out where I can. -- Kevin Horn ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] python-meta-packaging resource hub
On Mar 17, 2013 1:50 PM, "Marcus Smith" wrote: > > Kevin: > I added an initial readme, so pull requests work now. Good news. I'll send a pull req in a little while. > as for the compiler page I was talking about, here's the email that announced the page, and the github project for the src. > > http://mail.python.org/pipermail/python-announce-list/2013-February/009777.html > > it was just a thought. that tag icons and categories being the main reason it popped to mind. > If you're into sphinx and want to kickstart something for us like that, then you can now actually submit a pull. I've worked with Sphinx quite a bit. I'll check it out and see what I can manage. > barring that, I'll would likely just post a simple TOC structure later today or tomorrow that PEP people and project owners can start filling in. > Marcus > > > On Sat, Mar 16, 2013 at 5:30 PM, Marcus Smith wrote: >> >> Hello Kevin: >> I have admin access. I'll look at this in a bit. >> I'm trying to find a sphinx project that was posted recently that offered an index for compiler tools. >> that seemed to have a good template we could kickstart with >> can someone point us to where that was? >> Marcus >> >> On Sat, Mar 16, 2013 at 4:03 PM, Kevin Horn wrote: >>> >>> Howdy! >>> >>> I've been lurking on the list for a while, but have been pretty quiet so far. >>> >>> I was watching the live stream of the PyCon packaging panel today and the pytjon-meta-packaging resource hub idea was mentioned, which I hadn't heard of before, and was spurred to action. >>> >>> So I created a skeleton Sphinx project in a fork of this project here: >>> >>> https://bitbucket.org/khorn/python-meta-packaging >>> >>> Sadly, bitbucket won't let me do a pull request for some reason. If anyone knows why that is, feel free to let me know. >>> (FYI I think it's because the main repo has no commits in it, which makes the "Create a pull request not load properly.) >>> >>> At any rate, somebody somewhere should feel free pull it into the main repo, so we can get things moving on that front. I'm happy to help out where I can. >>> >>> -- >>> Kevin Horn >>> >>> ___ >>> Distutils-SIG maillist - Distutils-SIG@python.org >>> http://mail.python.org/mailman/listinfo/distutils-sig >>> >> > ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] python-meta-packaging resource hub
On Sun, Mar 17, 2013 at 7:48 PM, Kevin Horn wrote: > > On Mar 17, 2013 1:50 PM, "Marcus Smith" wrote: > > > > Kevin: > > I added an initial readme, so pull requests work now. > > Good news. I'll send a pull req in a little while. > OK, so initially I ran into "repository is unrelated", apparently because I forked before there were any commits in the upstream repo. So I re-forked, moved over my changes, and tried to make another pull request, and now I get a big "Access Denied" message. Is there some permission I need just to submit a pull request? I've never run into that before... -- Kevin Horn ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] python-meta-packaging resource hub
On Sun, Mar 17, 2013 at 7:48 PM, Kevin Horn wrote: > > On Mar 17, 2013 1:50 PM, "Marcus Smith" wrote: > > > > Kevin: > > I added an initial readme, so pull requests work now. > > Good news. I'll send a pull req in a little while. > > > as for the compiler page I was talking about, here's the email that > announced the page, and the github project for the src. > > > > > http://mail.python.org/pipermail/python-announce-list/2013-February/009777.html > > > > it was just a thought. that tag icons and categories being the main > reason it popped to mind. > > If you're into sphinx and want to kickstart something for us like that, > then you can now actually submit a pull. > > I've worked with Sphinx quite a bit. I'll check it out and see what I can > manage. > > > barring that, I'll would likely just post a simple TOC structure later > today or tomorrow that PEP people and project owners can start filling in. > > Marcus > > > > I checked out the compiler page a bit, and it looks like they're using markdown and pandoc to build that site. We can probably put something together that is somewhat similar, if we like, though it would be helpful to know what features of that site were the ones that people liked. I can put together a Sphinx theme if we want a custom one, and maybe some custom ReST directives as Sphinx extensions if we want to go that far. What is it that people want to see with this site? -- Kevin Horn ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] python-meta-packaging resource hub
On Sun, Mar 17, 2013 at 9:10 PM, Kevin Horn wrote: > On Sun, Mar 17, 2013 at 7:48 PM, Kevin Horn wrote: > >> >> On Mar 17, 2013 1:50 PM, "Marcus Smith" wrote: >> > >> > Kevin: >> > I added an initial readme, so pull requests work now. >> >> Good news. I'll send a pull req in a little while. >> > > OK, so initially I ran into "repository is unrelated", apparently because > I forked before there were any commits in the upstream repo. > > So I re-forked, moved over my changes, and tried to make another pull > request, and now I get a big "Access Denied" message. > > Is there some permission I need just to submit a pull request? I've never > run into that before... > > Ugh, ignore this. I was clicking the pull request button in the wrong window... Pull request sent. (finally) -- Kevin Horn ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] The pypa account on BitBucket
On Wed, Mar 20, 2013 at 12:39 PM, Marcus Smith wrote: > Nick: > > I'm not sure who owns it yet. > If it is one of us, then it would need to be a group vote to use the pypa > "brand name" like this. > I'll try to get all the pypa people to come here and register their > opinion. > > here's my personal thoughts: > > I understand the motivation to reuse our name, but probably less political > to start a new nifty short name. > "pypack" or something. "pack" as in a group of people, but also short for > "packaging" > > I like the "pypack" name. > In the spirit of the blog post, here's the 2 doc projects I'd like to see > exist under this new ~"pypack" group account, and be linked to from the > main python docs. > > 1) "Python Packaging User Guide": to replace the unmaintained > Hitchhiker's guide, or just get permission to copy that in here and get it > up to date and more complete. > 2) "Python Packaging Dev Hub": a simpler name to replace > "python-meta-packaging" > > give the ~10-15 people that are actively involved in the various packaging > projects and PEPs admin/merge access to help maintain these docs. > > and then announce this on python-announce as real and supported indirectly > by the PSF. > > people will flock IMO to follow it and contribute with pulls and issues > > Marcus > This sounds like a reasonable plan to me. There definitely need to be a user-centric bunch of docs being maintained someplace. -- Kevin Horn ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
