[20:43:07] <doismellburning> zahlman: yep, but I'll need more detail than that to be able to help ;)
[20:43:52] <zahlman> ok, first wanted to see if there actually was anyone. :) I'm trying to test what will happen when others install my project, by using virtualenv
[20:44:05] <zahlman> I created and activated a virtualenv, and attempt `py setup.py install`
[20:45:14] <zahlman> there are two problems: 1. the data goes to my main python installation instead of the sandbox; 2. the .egg file is copied into lib/site-packages, but no actual .py or .pyc files seem to make it (so I can't actually import the project or run the scripts)
[20:47:03] <doismellburning> zahlman: can you elaborate upon "the data goes to my main python installation" and "no actual [..] files seem to make it" please? (Ideally by gist-ing a console session showing you doing the whole lot - creation, activation, installation)
[20:48:24] <zahlman> sure thing... let me just pick the relevant parts out of my command history
[20:58:33] <doismellburning> cribbing from http://stackoverflow.com/q/304319/928098
[20:58:47] <zahlman> ... hrm. of course that doesn't know about my sandbox. python for windows doesn't install that in the python directory because of technical reasons
[20:59:11] <doismellburning> I know little about Windows
[20:59:14] <zahlman> ...I didn't realize `where` works on windows o_O it's at C:\Windows\py.exe, as I expected
[20:59:26] <doismellburning> right, yep, you're not using your virtualenv's python etc.
[20:59:32] <tomprince> zahlman: It is often best to just ask your question, and then stick around for a while, and then people can answer when they get back to their computer.
[20:59:53] <doismellburning> I've never heard of pylauncher, so good luck, but this should point you in the right direction
[21:00:12] <zahlman> tomprince: normally I do this in channels that seem a little more active :)
[21:01:52] <doismellburning> zahlman: generally lurkers outnumber active users for most channels ;)
[21:02:47] <zahlman> anyway, that seems to have put the files into the sandbox properly, but I still have the problem that the .egg is copied without any source files.
[21:03:39] <doismellburning> I'm afraid I know little about eggs, but would suggest pastebinning your setup.py
[21:04:21] <zahlman> I'm definitely not married to eggs. it's just what came out of setup.py install
[21:06:01] <tomprince> zahlman: It is actually more useful in channels that are less active, since the people who can answer may be in a different time zone.
[21:06:22] <tomprince> It does mean that you should close your IRC connection for at least a day or so.
[21:06:57] <doismellburning> tomprince: I assume you mean "shouldn't" ;P
[21:09:15] <pmxbot> you're doing good work, pmxbot!
[21:09:30] <zahlman> argh... not having a fun time with the gist editor. it does not copy and paste well
[21:09:35] <buck1> dstufft: rewinding a bit: Do I have to refactor find_requirement in order to avoid these http requests? http://paste.pound-python.org/show/RwHTReR3Az70tZUt6qUh/
[21:09:59] <buck1> zahlman: uncheck the "ACE Editor" box
[21:11:36] <buck1> the first two i think you've tried to address in your recent proposal
[21:22:05] <buck1> "." being the current directory, assuming you've cd'd to it during dev
[21:22:19] <zahlman> unfortunately, pip isn't working in my virtualenv sandbox either. :(
[21:22:48] <buck1> a lovely talk https://www.destroyallsoftware.com/talks/boundaries
[21:22:56] <buck1> i'm going to see if i can't make pip look more like tihs
[21:23:01] <zahlman> I'm getting a message like `Fatal error in launcher: Unable to create process using '""C:\path\to\sandbox\Scripts\python.exe"" "C:\path\to\Scripts\pip.exe" install .'`
[21:23:09] <zahlman> note the extra double-quotes around the python path.
[21:30:59] <zahlman> anyway, in terms of distribution, the general idea is that the whole project folder (modulo .gitignore) goes on github, and the results of sdist/bdist_wheel go on PyPI, yes?
[21:31:48] <zahlman> (I'm actually entirely new to actually using tools for this, as opposed to just sending people my .py files. Rather embarrassing, really.)
[21:32:17] <buck1> you can also install with git+ urls if you want to avoid pypi, generally during prototyping
[21:32:31] <aclark> zahlman: re: [20:45:14] <zahlman> there are two problems: 1. the data goes to my main python installation instead of the sandbox; 2. the .egg file is copied into lib/site-packages, but no actual .py or .pyc files seem to make it (so I can't actually import the project or run the scripts)
[21:32:53] <aclark> the answer to 1 is likely "wrong python". if you use the python from the virtualenv then that's where your package should be installed
[21:33:01] <buck1> aclark: the solution to eggs was pip, but his pip crashes
[21:33:39] <zahlman> yep. It was the wrong python because of windows stuff (the tools they give you to use 2.x and 3.x on the same machine, unfortunately have no concept of virtualenv apparently.)
[21:33:41] <aclark> and the answer to #2 is likely "broken package" meaning no packages=find_packages() or something else not configured properly
[21:34:25] <zahlman> my packages end up as ['src'], and I do have that folder with an __init__.py etc. in it
[21:34:26] <aclark> zahlman: also there is no "use of eggs", I'm not sure why py setup.py install creates an egg… does python setup.py install do the same thing?
[21:39:59] <zahlman> er, how do I check? I'm getting the package version instead.
[21:42:20] <zahlman> ... hrm. per the dist-info folders in site-packages, the sandbox appears to have 3.6, whereas the main python installation appears to have 2.1. o_O
[21:46:50] <aclark> zahlman: look in site-packages
[22:07:43] <zahlman> the usual Windows kludge seems to have done it (ensure no spaces in path)
[22:22:41] <zahlman> ok, pip is building the project fine now, although it spews out a long trace at the end because it failed to delete some temp files.