Posted
1 day
ago
by
ch-athens
For older Zope versions it is still necessary to use Python 2.4 versions. To compile Python 2.4
on Mac OS X Snow Leopard, I had to jump through a few little hoops: First I downloaded and
unpacked the python tarball, then I applied the following patch...
Posted
1 day
ago
by
RedTurtle Technology
The way I used to make Flowplayer use inside Plone a little more accessible, this time without branching the collective.flowplayer product!
Posted
3 days
ago
by
Martin Aspeli
Posted
3 days
ago
by
Lennart Regebro: Plone consulting
Posted in plone, python Tagged: copyright, music, open source, patents
Posted
5 days
ago
by
Zea Partners News
Xavier Heymans, CEO of Zea Partners, has been appointed to the Plone Foundation's advisory board.
Posted
5 days
ago
by
Reinout van Rees' weblog
If you import from it, you must mention it as a dependency in your
setup.py
?
Some imports work just fine as another dependency depended on the thing you're
importing. Still, it is safer to also include that dependency if you use
... [More]
it
directly: if the dependencies get refactored (for instance the large-scale
cleanup in zope's libraries), the indirect dependency might not help you out
anymore.
. Install it and run
"dependencychecker" inside your python project. It will report on:
: pyflakes is another tool that does this (and that also
reports on missing variables inside the files).
: imports without a corresponding requirement
in the . There might be false alarms, but at least you've got a
(hopefully short) list of items to check.
Watch out for packages that have a different name than how they're imported.
For instance a requirement on in
your code: pydns and DNS lead to separate "missing requirements: DNS" and
"unneeded requirements: pydns" warnings.
: requirements in your setup.py that aren't
imported anywhere in your code. You need them because not
everything needs to be imported. It at least gives you a much smaller list
to check by hand.
: if something is only imported in
a test file, it shouldn't be in the generic defaults. So you get a separate
list of requirements that should be moved from the regular to the test
requirements. (Since version 0.3).
is treated as a
requirement for
package. () And before you
remove something, please grep around a bit. Doctests also aren't checked yet.
(
It is already helping me in cleaning up grok's dependencies. Grok uses the
zope tool kit's libraries and they've seen some major dependency refactoring.
Grok 1.1 is supposed to reap the fruits of that. But for that to happen,
grok's own requirements need to be right, of course. So I'm now going through [Less]
Posted
8 days
ago
by
Reinout van Rees' weblog
Regularly trying out new technologies is essential for programmers. Knowledge
becomes stale. The technology landscape changes all the time.
just
as I was re-reading the great book. And there's
one tip from that book that I
... [More]
haven't done yet in all those years: learn one
new language per year. I kept thinking about that and decided to make a list
of new things I tried out this year.
Distributed version control. I tried bzr earlier and this year I tried out
mercurial (hg) and git. I even added git support to zest.releaser. And I
started using hg for some personal projects. I'm debating a change back to
bzr for my personal stuff because of easier handling of the "centralized"
subversion-like workflow in bzr. Anyway: lots of experimenting and
trying-out so that I know what these kind of systems can do.
Buildbot! I spend some quality time earlier this year setting up automated
testing. Looking at the test setup of all our internal projects and making
sure everything ended up in tip-top shape.
Grok. Coming from Plone early this year, I now work full-time with grok. A
different python web framework, so that was a pretty big change.
Wordpress. PHP. A volunteer website project, which was already set up with
wordpress. I support it, so I had to look at PHP again after not using it
for 8 years.
Setuptools-related: collective.eggproxy (pypi caching), zc.buildout addition
and one fix, distribute fixes. You get a peek under the hood and learn some
more about the inner workings. Useful knowledge.
Layout: I made a layout with the YUI css framework last year and
experimented with blueprint this year. And I tried out font
embedding. Now (begin December) reinout.vanrees.org uses some external
javascript for font embedding, but I'm going to put it directly into my css
once I picked a decent font.
A new personal non-plone website meant figuring out Sphinx and making custom
restructuredtext statements. And looking better at deliverance (and for
another website, at xdv).
Jquery. I'm too stuck in regular html webpages by default. I almost do
much on the server side. The last time I touched javascript directly is
a few years ago! So getting up to speed with jquery effectively means I learn
another programming language :-)
Trying out BFG for a small project. Another minimalistic web framework.
Broaden my horizon! [Less]
Posted
9 days
ago
by
Martin Aspeli
Posted
10 days
ago
by
Plone News
We will be entering a maintenance window this weekend to work on an upgrade of the Plone Help Center.
Posted
10 days
ago
by
Martin Aspeli
