Hi All,
I saw lots of failures on Windows, but I guess that's 'cos I need to
have a C-compiler, right?
Anyway, even on Linux there were still these failures with python 2.4.5:
$ bin/test
Running zope.testing.testrunner.layer.UnitTests tests:
Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
zip_safe flag not set; analyzing archive contents...
zip_safe flag not set; analyzing archive contents...
zip_safe flag not set; analyzing archive contents...
zip_safe flag not set; analyzing archive contents...
zip_safe flag not set; analyzing archive contents...
zip_safe flag not set; analyzing archive contents...
Failure in test test_bootstrap_py (zc.buildout.tests)
Failed doctest test for zc.buildout.tests.test_bootstrap_py
File "/home/chris/zc.buildout/src/zc/buildout/tests.py", line 581, in
test_bootstrap_py
----------------------------------------------------------------------
File "/home/chris/zc.buildout/src/zc/buildout/tests.py", line 592, in
zc.buildout.tests.test_bootstrap_py
Failed example:
print system(zc.buildout.easy_install._safe_arg(sys.executable)+' '+
'bootstrap.py'), # doctest: +ELLIPSIS
Expected:
Downloading ...
Generated script '/sample/bin/buildout'.
Got:
Creating directory '/sample/bin'.
Creating directory '/sample/parts'.
Creating directory '/sample/eggs'.
Creating directory '/sample/develop-eggs'.
Generated script '/sample/bin/buildout'.
----------------------------------------------------------------------
File "/home/chris/zc.buildout/src/zc/buildout/tests.py", line 609, in
zc.buildout.tests.test_bootstrap_py
Failed example:
ls(sample_buildout, 'eggs')
Expected:
- setuptools.eggpyN.N.egg
d zc.buildout.eggpyN.N.egg
Got:
d setuptools.eggpyN.N.egg
d zc.buildout.eggpyN.N.egg
zip_safe flag not set; analyzing archive contents...
Ran 353 tests with 1 failures and 0 errors in 4 minutes 22.881 seconds.
Tearing down left over layers:
Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
At 06:23 PM 8/12/2008 +0100, Fadhley Salim wrote:
>Phillip,
>
>Thanks for your help - still no go!
>
>Any time I give it a web URL (e.g. http://something) it works fine. If I
>give it something else, it seems to get confused - there's no evidence
>that it's even looking at my folder.
>
>I'm trying to do something like this:
>
>easy_install -m calyon-tools==1.0-r2008-0630-trunk-3968
>--find-packages="//sald441/webapps/eggs/tools_egg/"
There is no such option as "--find-packages"; it's "-f" or
"--find-links". Also, you should not include a trailing '/' or '\'
when specifying file paths.
If you want to check whether a directory is being processed, increase
the verbosity of setuptools output to at least '-vv'; then you should
see a series of "Found:" lines appear listing the contents of the
target directory.
Hi All,
Looks like something weird is happening:
C:\aproject\trunk>python bootstrap.py
<snip>
C:\aproject\trunk>bin\buildout.exe
Getting distribution for 'zc.buildout'.
Getting distribution for 'setuptools'.
Got setuptools 0.6c8.
Got zc.buildout 1.1.1.
C:\aproject\trunk>Upgraded:
zc.buildout version 1.1.1,
setuptools version 0.6c8;
restarting.
At this point here, it looks like buildout is running in some kind of
backgrounded process, which means that:
- if I hit enter while it's still progressing, I get things like:
"""
Getting distribution for 'zope.testing'.
C:\aproject\trunk>
C:\aproject\trunk>
C:\aproject\trunk>Got zope.testing 3.6.0.
bin\ bin\buildout.exeGetting distribution for
'zope.interface'
. Got
zope.interfa
"""
- I don't know when buildout is finished because the command prompt was
echoed way back in the middle of things.
NB: This only appears to happen the first time setuptools and buildout
are installed. Further run of bin\buildout don't exhibit this behaviour.
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
Hi All,
I'm reading http://pypi.python.org/pypi/zc.recipe.egg#script-generation
with a hope to finding out how to write an egg such that I can have mroe
own scripts generated and called.
I think having a read of the demo egg used in these tests would solve my
problems, but where does it live?
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
At 04:41 PM 8/12/2008 +0100, Fadhley Salim wrote:
>What about using a network folder, e.g. a UNC path? Were you able to get
>such a thing working ever?
I've heard of people using network folders; I'm not sure I've
personally tried a UNC path. Keep in mind that command-line
quoting/escaping can foul up your backslashes, though, so I would
suggest trying using '/' in place of '\' in your command line. That
is, '//server/share' instead of '\\server\share'.
>-----Original Message-----
>From: Phillip J. Eby [mailto:pje@telecommunity.com]
>Sent: 12 August 2008 16:15
>To: Salim, Fadhley (CALYON); distutils-sig(a)python.org
>Subject: Re: [Distutils] Distutils / Setuptools on Windows: Can we use
>local or UNC filesystems as an argument to --find-links
>
>At 03:46 PM 8/12/2008 +0100, Fadhley Salim wrote:
> >Has anybody had any luck using the --find_options argument to
> >easy_install with a local folder (e.g. on a Windows C: Drive) or a
> >network folder, for example
> >
> >easy_install --find-links="http://server/egs" myegg==1.0.1 ( that sort
> >of thing works fine )
>
>So should this:
>
> >easy_install --find-links="c:\myeggs\" myegg==1.0.1
>
>The file:// urls can work too, but they work differently than just using
>a directory filename; they'll be checked at a later stage of processing.
>And of course, they're harder to get right. :)
>>
>> Specifically, I want to be able to add a configuration and build some
>> classes only if one of these commands is specified.
>
> what are you trying to do precisely ?
>>
In a setup.py, there's a method that builds some classes and puts them
in a zip file. Then there's a line
config.add_data_files(this_method)
The method doesn't need to be called when only a source distribution
is being created. I was hoping there might be a way to switch this
config line off if there's no need for it, or maybe only switch it on
when it is needed (something beyond using sys.argv).
At 03:46 PM 8/12/2008 +0100, Fadhley Salim wrote:
>Has anybody had any luck using the --find_options argument to
>easy_install with a local folder (e.g. on a Windows C: Drive) or a
>network folder, for example
>
>easy_install --find-links="http://server/egs" myegg==1.0.1
>( that sort of thing works fine )
So should this:
>easy_install --find-links="c:\myeggs\" myegg==1.0.1
The file:// urls can work too, but they work differently than just
using a directory filename; they'll be checked at a later stage of
processing. And of course, they're harder to get right. :)
Hello all. I had some spare time the other day and went through the
tracker, reclassifying a few things and marking some with a
"needpatch" keyword. The ones marked "needpatch" vary from things I
have no idea what to do with, to ones where I've practically spelled
out the needed patch in the tracker.
Issues with patches that passed my initial review have been marked
"in-progress"; these could use some testing before check-in. At this
point, I haven't had an opportunity to review the results of the test
sprint that was done; if somebody could throw that up as a patch on
the tracker, or at least repost a link to where I can find that
stuff, that would help.
All of this is with an eye to releasing an 0.6 final in the near
future; sometime this month I'd guess/hope, depending on how my other
projects are going.
Hi,
I just finished my first egg, but have a question:
How can I distribute example scripts for my
package ???
Greetings, Uwe
--
Dr. rer. nat. Uwe Schmitt
F&E Mathematik
mineway GmbH
Science Park 2
D-66123 Saarbrücken
Telefon: +49 (0)681 8390 5334
Telefax: +49 (0)681 830 4376
uschmitt(a)mineway.de
www.mineway.de
Geschäftsführung: Dr.-Ing. Mathias Bauer
Amtsgericht Saarbrücken HRB 12339
A project I'm working on requires a Python egg to be deployed to a
remote location which (because of a security configuration outside my
control) denies users access to the web-servers we use to load eggs from
the office I work.
I've determined that the security at this location allows users access
to Windows networked file-systems. It has been proposed that rather than
creating a web-repository for python eggs we store these on a local
file-server. But from what I can tell the easy_install utility can ONLY
load it's eggs from web-servers.
Has anybody had any luck using the --find_options argument to
easy_install with a local folder (e.g. on a Windows C: Drive) or a
network folder, for example
easy_install --find-links="http://server/egs" myegg==1.0.1
( that sort of thing works fine )
but what about:
easy_install --find-links="c:\myeggs\" myegg==1.0.1
or even:
easy_install --find-links="file:///c:/myeggs" myegg==1.01
and with a UNC path:
easy_install --find-links="file://///myserver/webapps/eggs/" myegg==1.01
If (as I suspect) easy_install cannot support anything other than a
direct-http set-up is there a way for me to simply modify the code for
easy_install to do this? Furthermore, since we like to be up to date I
dont want to run a permanently forked version of setuptools - can we
submit any changes back to the project so we do not have to be
permanently forked?
Thanks
This email does not create a legal relationship between any member of the
Crédit Agricole group and the recipient or constitute investment advice.
The content of this email should not be copied or disclosed (in whole or
part) to any other person. It may contain information which is
confidential, privileged or otherwise protected from disclosure. If you
are not the intended recipient, you should notify us and delete it from
your system. Emails may be monitored, are not secure and may be amended,
destroyed or contain viruses and in communicating with us such conditions
are accepted. Any content which does not relate to business matters is not
endorsed by us.
Calyon is authorised by the Commission Bancaire in France and regulated by
the Financial Services Authority for the conduct of business in the
United Kingdom. Calyon is incorporated in France with limited liability
and registered in England & Wales. Registration number: FC008194.
Registered office: Broadwalk House, 5 Appold Street, London, EC2A 2DA.
