I've really tried.. win install .7b3
dartdog
offer my 2 cents worth..And I know I should use and love Linux ( and I
do but I need windows here) but my commercial target audience will
require windows, even on the dev side...which is one of the strengths
of Python /Django (platform transparency)
And I really do want to use this stuff I think it looks great and I
think has a ton of potential so what follows is my attempt at
something of constructive contribution, not critical...
The packaging complexity completely prevents some from tying to use
the system or even parts.
After carefully going though the messages her and applying the several
mentioned hacks, and a few other nudges... I almost got it going.
IMHO You are trying to do way too much with the install process. How
about breaking it up and documenting what the results should be.
Also as a few have noted with the sort of monolithic install process
updates are impossible or at least very scary,,,
While it may appear that virtual env fixes things it adds yet another
layer of abstraction, and path confusion.
All I want is a set of install instructions for Django and required
packages and locations...I believe I can find and install stuff...
At this point in my experiment the system has generated a sample app
in my root directory and cannot find Pinax to import it so cannot run
sync db..
I tried moving the sample back into a pinax directory (back in my
eclipse workspace) but no luck so far...Also when running install the
install could not locate the geo-dango stuff on google code.. see
below I did have some other ,I think, less consequential errors...
Running command svn checkout http://geopy.googlecode.com/svn/trunk/ c:
\users\dadlap~1\appdata\local\temp\pip-pd0obs-build
Error [Error 2] The system cannot find the file specified while
executing command svn checkout http://geopy.googlecode.com/svn/trunk/
c:\users\dadlap~1\appdata\local\temp\pip-pd0obs-buil
Skylar Saveland
While it may appear that virtual env fixes things it adds yet another
layer of abstraction, and path confusion.
Well, the virtualenv stuff is brilliant imho.
All I want is a set of install instructions for Django and required
packages and locations...I believe I can find and install stuff...
There are a couple of text files that tell you what the dependencies are but there are many. I did it by hand without the install script once and never again.
At this point in my experiment the system has generated a sample app
in my root directory and cannot find Pinax to import it so cannot run
sync db..
The virtualenv has not been activated? What happens when you try to source the activation script? I guess you did run clone_project successfully though?
I tried moving the sample back into a pinax directory (back in my
eclipse workspace) but no luck so far...Also when running install the
install could not locate the geo-dango stuff on google code.. see
below I did have some other ,I think, less consequential errors...
Running command svn checkout http://geopy.googlecode.com/svn/trunk/ c:
\users\dadlap~1\appdata\local\temp\pip-pd0obs-build
Error [Error 2] The system cannot find the file specified while
executing command svn checkout http://geopy.googlecode.com/svn/trunk/
c:\users\dadlap~1\appdata\local\temp\pip-pd0obs-buil
Geopy is not geodjango. Best of luck; I don't know anything about windows though, sorry.
Brian Rosner
>
> I am amazed and impressed by what is going on here but would like to
> offer my 2 cents worth..And I know I should use and love Linux ( and I
> do but I need windows here) but my commercial target audience will
> require windows, even on the dev side...which is one of the strengths
> of Python /Django (platform transparency)
We agree that Windows compatibility is critical. Keep in mind that we
are working on getting support, but we are slow to this because *non*
of the core developers use Windows. I understand Windows is an
important platform, but you have to understand where we are coming
from and we are really deferring to the community to step up and help
us fix Windows.
I really appreciate the time and work you have put in to helping us
out. It means a lot to us and the Pinax Windows community.
> The packaging complexity completely prevents some from tying to use
> the system or even parts.
> After carefully going though the messages her and applying the several
> mentioned hacks, and a few other nudges... I almost got it going.
>
> IMHO You are trying to do way too much with the install process. How
> about breaking it up and documenting what the results should be.
I would disagree to an extent. I absolutely agree we are generally
installing too many dependancies up front. It is something we want to
tone down and make it simpler to get running on a specific project.
However, in many cases for our users, they don't know what project
they want. We compromise at this point to install everything and let
them decide.
The Windows platform has a great opportunity for us to do some great
things. I can imagine we have a installer that can deal with many of
this stuff under the hood. However, I don't even know where to begin
with that. I see Windows actually being the easiest platform to use
Windows. The desire needs to be there in the community to step up and
really make Pinax kick ass on Windows.
>
> While it may appear that virtual env fixes things it adds yet another
> layer of abstraction, and path confusion.
The virtual environment bit is absolutely critical in dealing with
Pinax. Due to the major amounts of dependancies we depend on keeping
an isolated environment of them so that different projects can rely on
different versions is critical. I also think forcing this up front is
a good thing for the end-user (being the site developer) because it is
a tool that should be every Python developer's toolbox (IMO).
>
> All I want is a set of install instructions for Django and required
> packages and locations...I believe I can find and install stuff...
>
We have requirement files that outline each dependancy in a human
readable format. Look at requirements/external_apps.txt and
requirements/libs.txt.
>
> Running command svn checkout http://geopy.googlecode.com/svn/trunk/ c:
> \users\dadlap~1\appdata\local\temp\pip-pd0obs-build
> Error [Error 2] The system cannot find the file specified while
> executing command svn checkout http://geopy.googlecode.com/svn/trunk/
> c:\users\dadlap~1\appdata\local\temp\pip-pd0obs-buil
Do you have Subversion installed and accessible on the PATH?
--
Brian Rosner
http://oebfare.com
dartdog
After downloading the trunk version as of 6/23/09
I found I had to make the following mods to get pinax-boot.py to run
at all.. See attached version which has notations on the changes but a
diff editor would be the easiest way to see.
Opps It looks like no file attachments...so I put it here
http://code.pinaxproject.com/paste/mnxC/
With those changes it seems to run
dartdog
jpeg, but no place to put it....
Let me know and I'll post it.
Then I'll go through the rest step by step...
dartdog
only activate it in the command shell and then I'm sort of stuck with
that environment, not sure how to configure it for use within
Eclipse.. Which would be "much" more helpful...
On Jun 24, 4:50 pm, dartdog <tombran...@gmail.com> wrote:
> I'll give a go at documenting what is happening...
> After downloading the trunk version as of 6/23/09
> I found I had to make the following mods to get pinax-boot.py to run
> at all.. See attached version which has notations on the changes but a
> diff editor would be the easiest way to see.
Daniel Greenfeld
>>
>> While it may appear that virtual env fixes things it adds yet another
>> layer of abstraction, and path confusion.
>The virtual environment bit is absolutely critical in dealing with
>Pinax. Due to the major amounts of dependancies we depend on keeping
>an isolated environment of them so that different projects can rely on
>different versions is critical. I also think forcing this up front is
>a good thing for the end-user (being the site developer) because it is
>a tool that should be every Python developer's toolbox (IMO).
virtualenv is critical! If you don't use it, each time you install a
new python package it adds to your python's site-packages directory.
Eventually two packages will collide in their choice of name spaces
and you'll have weird problems that are unbelievably difficult to
diagnose.
Before virtualenv (and zc.buildout) the solution to this was multiple
python installations. Which can get sloppy really fast. Virtualenv
over zc.buildout was chosen by the Pinax core developers because of
personal preference, but that seems to have been for the best, since
zc.buildout is not nearly as well supported on Windows.
--
'Knowledge is Power'
Daniel Greenfeld
http://pydanny.blogspot.com
http://dannygreenfeld.blogspot.com
dartdog
and a directory of the result in imagebin
(11:18:17 AM) dartdog: Directory produced by pinax-boot.py
http://imagebin.org/53646
(11:19:54 AM) dartdog: If we need the console I can pastebin it also..
(11:20:38 AM) dartdog: And if this looks ok, I can run activate then
install...
On Jun 25, 7:40 am, Daniel Greenfeld <pyda...@gmail.com> wrote:
dartdog
mods...
See image shot...below
The reporting and interactivity here seems sort of strange,, I am
volunteering to work through the win install issue, which seems to be
acknowledged, I can't do on my own (lack of skills!) but the main
response is that no one in core has any win expertise, and I guess by
inference interest in getting this going on win, which could of course
get a bunch more better than me devs working on it. but the current
starting hurdle is pretty high...
So my offer is there, I'll try if I can get some guidance,, and that
will produce documentation.
On Jun 25, 11:31 am, dartdog <tombran...@gmail.com> wrote:
> Ok here is a transcript of my attempt to run pinax-boot.py
> and a directory of the result in imagebin
>
Brian Rosner
> The reporting and interactivity here seems sort of strange,, I am
> volunteering to work through the win install issue, which seems to be
> acknowledged, I can't do on my own (lack of skills!) but the main
> response is that no one in core has any win expertise, and I guess by
> inference interest in getting this going on win, which could of course
> get a bunch more better than me devs working on it. but the current
> starting hurdle is pretty high...
I don't have the time right now to devote to reading up what you have.
However, I am very grateful that you are helping. Give me a couple of
days and I'll give this much more direct attention. Thanks a ton!
dartdog
mention that Birthday! Have a happy one!
You can get me via twitter, I'm following
I'm going to give it a bit more and if I can't move it forward some on
my own ,, then move on to something a bit more comprehensible...'Till
I can get a hand...
Best,
FWIW the image of the directory will only be there for 7 days.. I can
repost...
On Jun 25, 12:13 pm, Brian Rosner <bros...@gmail.com> wrote:
dartdog
the Path... (I had been using Tortoisesvn, which does not provide a
command line interface, no exe only dll's....
That got me way further
But still at the end some failures,,,still have whole sections not
found.... The Pip log is rather large, pastebin: http://code.pinaxproject.com/paste/9m8Q/
it if that is best??
dartdog
Third!!! way more complete one, did not realize it was doing appends
instead of replace,,, sorry.
dartdog
get cannot import Pinax (not found.. Where is what I should point to,
I attempted to
place an entry into the system path variable,,, but I'm really not
sure what I should point to...
A hint on that might get me going... any idea what file/ folder
structure I need to point to , and how so Pinax import is correct?