Hi first thanks for your feedback. I am.sorry that it did not work out for you yet. I will look into it this evening and will write a littlebit more on this.
Torsten
--
You received this message because you are subscribed to a topic in the Google Groups "pylons-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pylons-discuss/v1JosQgO9OQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pylons-discus...@googlegroups.com.
To post to this group, send email to pylons-...@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
Hi, this looks very nice, but I am not able to get it running - the instructions in the 'get started' section of the website do not get me started, unfortunately.
ImportError: /home/xxx/.local/lib/python2.7/site-packages/lxml/etree.so: undefined symbol: PyUnicodeUCS4_DecodeLatin1
Argh, an unicode error, no, please not that kind of problems... I am giving up here for today.
I think I have to write about my experiences with several other pyramid based projects here. I have had similar problems with kotti and ptah in the recent past. I hope writing about it here will not be seen as ranting, but may give you an insight about the newcomer perspective.
I looked at pyramid and was extremely satisfied, this really looks like the best way to build websites (for me) after some years of experience with several other (non-python) frameworks. I am really deeply impressed about the approaches taken with pyramid and the extensive documentation, everything I see sets a really very high quality standard.
However, after some playing around of course I came to the point of not wanting to reinvent all the wheels, not only because I am a lazy dog, but because of the fear of doing things wrong. Especially all things security, like permissions, user signup and forms I really would like to build on something battletested, so I was starting to look into the several things that are out there and build up on pyramid, like kotti and ptah, and now ringo.
The most significant experiences with these have been that I was not able to get them running.
What is frustrating: I read a little bit into the sources, but I was not able to solve the problems. And what was even more frustrating was the knowledge, that this all is not some deeply involved hardcore hacker stuff that I am not understanding, it is all packaging and version isolation problems on the surface, so I feel like some little thing is keeping me away from usig all that great stuff because, of course, I can not build a real website with anything that throws errors I can not solve.
Ok, I know this is all my fault not studying all the details about the python setup process (BORING!) - but to make it a little bit more constructive I would like to ask all you great developers out there: please test your setup instructions, especially the ones on page one, manually and test them in a "fresh" python environment, test them with pyenv and several python versions, test them on a stock debian and ubuntu with system python, and please always link to the relevant knowledge about the setup process - please avoid magic that does not work.
--
You received this message because you are subscribed to a topic in the Google Groups "pylons-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pylons-discuss/v1JosQgO9OQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pylons-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
I gave it a try, too. MacOS X 10.10, Python 2.7.9 from MacPorts.
Everything worked fine.
> pcreate -t ringo foo
The doc says "pcreate -t ringo Foo" ("Foo" with a capital "F").
You have to remember that the filesystem on a Mac is case-insensitive
(but case-remembering). So, "foo-admin" and "Foo-admin" would be the
same on a Mac, but "foo-admin" wouldn't exist on e.g. Ubuntu Linux.
I believe the initial instructions were created on a Mac, because I saw
Omnigraffle files (a Mac-specific drawing app) when I did the "hg clone"
yesterday.
> ImportError:
> /home/xxx/.local/lib/python2.7/site-packages/lxml/etree.so: undefined
> symbol: PyUnicodeUCS4_DecodeLatin1
I believe it depends on whether Python was compiled with UCS2 or UCS4
Unicode strings. In that particular case, I suppose UCS2 was chosen. I
compiled lxml a number of times (on FreeBSD, Linuxes and OS X, and never
came across that error)
Anyway, anything went fine for me, I was able to launch the app, and
from there I didn't know where to go... :D
PS: I have my own development environment too, but I'm afraid it's not
ready for prime time...
> On Jan 2, 2015, at 17:25 , tamgo...@gmail.com wrote:
> but this gives me an error (see full traceback below):
>
> ImportError: /home/xxx/.local/lib/python2.7/site-packages/lxml/etree.so: undefined symbol: PyUnicodeUCS4_DecodeLatin1
This error is not something that is happening due to Ringo, this is because your etree.so is compiled against a different python version. Verify your installation of etree.
> Great! Thanks for your feedback and congratulation, you are the first
> official MacOS user of Ringo :) If there is anyone else who want to be
> the first one on other OS too then go for it. There are plenty options
> left ;)
OK, first on FreeBSD too, then ;)
More precisely, FreeBSD 9.3-RELEASE for amd64, and python 2.7.9.
> I believe the initial instructions were created on a Mac, because I saw
> Omnigraffle files (a Mac-specific drawing app) when I did the "hg clone"
> yesterday.
> >
> No. It was some Linux System. Which files do you mean?
I'm not 100% sure, but I think I noticed one *.graffle file during the
"hg clone". But maybe it was in the "develop" phase, and I saw it in
another module...
> That's fine. Did you follow the instructions on the webpage or the ones
> from Steve?
From the webpage, http://ringo-dev.intevation.de/
> Did the creation of the modul work for you? There is currently a issue
> with that which i noticed in the instructions.) Do you seethe created
> module entry on the header menu of your application after logging.
No particular issue, meaning creation worked, and the app still runs,
but I can't see the bar module. So it seems it didn't work after all...
(just tested on FreeBSD).
> The next step is to add fields to the module to actually save something
> useful and build a nice form for it. This is described in the documentation:
>
> http://ringo.readthedocs.org/en/latest/development.html#adding-new-fields-to-the-model
Thanks, I'll have a look at it :)