1.04 file upload encode problem, did it get resolved?
iain duncan
upload field is this one:
http://groups.google.com/group/turbogears/browse_thread/thread/fa9209cd044bc454
But the latest 1.04 in the cheeseshop does not seem to fix it. Did this
get resolved? If I need this working pronto, should I revert to tg1.03?
Thanks
iain
iain duncan
Responding to myself here, the latest beta version from the tgsetup-beta
script or the cheeseshop is 1.04b3. In the thread above, a 1.04b4 was
supposed to be coming to fix this issue. The problem was reported as
known, breaking many apps, and ( apparently ) patched, on Dec 13, almost
a month ago. But that is not what we are getting installing TG.
IMHO, this is bad release management. There is no way we are going to
impress anyone having the default install for TG be broken like this. If
it doesn't work, and we know it, then please please, don't make an
easy_install TurboGears
or
tg-setup.py
install a broken beta! This is crazy. The default install should be
tg1.03 until we know 1.04 is fine, and if we find out we need to revert,
so be it.
Sorry to rant, but these kind of issues do sooo much public image
damage, I really think they need a lot more attention. This is the kind
of area in which Django and Rails walk all over us. :/
Iain
Florent Aide
Should be fixed in SVN (head of 1.0 branch)
Florent Aide
>
> IMHO, this is bad release management. There is no way we are going to
> impress anyone having the default install for TG be broken like this. If
> it doesn't work, and we know it, then please please, don't make an
>
> easy_install TurboGears
Yep. This is right. I am struggling with my time (or lack of...) to
get to be able to work on tg ATM. But if you know a way we could have
easy_install _not_ pick beta releases but only stable ones I would be
grateful.
As for the next release we are trying to sync up something with Chris
Arndt to make this happen this week. Sorry for the inconvenience.
Florent.
iain duncan
It is, I found that out. And i hope you don't think I meant my comments
personally. But I still maintain that is is a very bad situation that
someone new comes to turbogears, uses
easy_install TurboGears
( my default action for trying out any python library )
and gets a broken beta install that has been that way for month. If I
were a new user, the experience would be a real turn off, know what I
mean? I really appreciate all the work you have done, but that situation
looks really bad to a new TG user. I've taught two new users to TG now,
and the common theme is that it was way too hard to get it going.
I think one should have to go out of one's way to install potentially
broken versions. If we have a critical bug in a release, it should stay
as a tag in svn only and not be something that someone could
accidentally install via cheeshop. Sure that's just my opinion, but I do
honestly think that this is an area where TG has consistently shot
itself in the foot when it comes to marketing and public relations.
my two cents
iain
iain duncan
Well, what if we keep beta releases out of the cheeseshop altogether and
put clear instructions up on checking them out from svn? If it were me,
I'd make beta candidates be tags, because if I go to a new project, and
I check out a release candidate tag from svn, I *know* that it might not
work right. But if I install something automagically, I get really
annoyed if it isn't release quality because I don't really know what the
heck that automated release is putting where.
Thoughts?
Iain
Florent Aide
> Well, what if we keep beta releases out of the cheeseshop altogether and
> put clear instructions up on checking them out from svn? If it were me,
> I'd make beta candidates be tags, because if I go to a new project, and
> I check out a release candidate tag from svn, I *know* that it might not
> work right. But if I install something automagically, I get really
> annoyed if it isn't release quality because I don't really know what the
> heck that automated release is putting where.
>
> Thoughts?
Why not. I am open to make 1.x branch be the lighter burden I can...
but giving out eggs and having some tests on the install procedure is
also part of the release cycle. I would prefer to find a naming scheme
or option for easy_install that makes sure our beta releases are not
picked up.
Anyway I see the problem with having the default install picked by
easy_install not working perfectly...
Florent.
Christopher Arndt
> Well, what if we keep beta releases out of the cheeseshop altogether and
> put clear instructions up on checking them out from svn?
We could still have a tg-setup-beta.py script for them, but we would
need to provide a different download page for the eggs, so that the
tg-setup.py for stable versions doesn't pick up the beta eggs.
> If it were me,
> I'd make beta candidates be tags,
Beta releases are tagged in SVN.
Chris