On Sat, 2009-12-05 at 05:45 -0700, Peter A. Bigot wrote: > Two things: > > Based on this, I went ahead and put the base release back up on PyPI. > Try using "PyXB==base-1.1.0" instead. There are no bundles in that, so > you might avoid the problem there. >
Okay, this kind of works. It seems to be in the naming of the files. If I put PyXB in setup.py then PyXB = base-1.1.0 in versions.cfg (this is a Grok setup) Then it finds it and installs. However, it seems that it gets confused because it installs PyXB-1.1.0-py2.6.egg but then it thinks it installed a different version (missing 'base'?) So, it cycles through again. The only way to stop the circular install is to use CTL-C Here's the output. ============================================ Getting distribution for 'PyXB==base-1.1.0'. /tmp/easy_install-rjdPc5/PyXB-1.1.0/pyxb/utils/utility.py:582: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha warning: no files found matching 'MANIFEST' no previously-included directories found matching 'pyxb/bundles/core/schemas' no previously-included directories found matching 'pyxb/bundles/core/remote' no previously-included directories found matching 'pyxb/bundles/wssplat/schemas' no previously-included directories found matching 'pyxb/bundles/wssplat/remote' no previously-included directories found matching 'pyxb/bundles/opengis/schemas' no previously-included directories found matching 'pyxb/bundles/opengis/remote' no previously-included directories found matching 'doc/_build' warning: no previously-included files found matching 'doc/*.eap' no previously-included directories found matching 'doc/W3C' warning: no previously-included files matching '*~' found anywhere in distribution zip_safe flag not set; analyzing archive contents... pyxb.namespace.archive: module references __file__ Installing PyXB base-1.1.0 Caused installation of a distribution: PyXB 1.1.0 with a different version. Got None. Installing i18n. i18n: setting up i18n tools Getting distribution for 'PyXB==base-1.1.0'. ============================================ So maybe???? in the nameing in the egg info should match the file name so instead of getting PyXB-1.1.0-py2.6.egg I should get PyXB-base-1.1.0-py2.6.egg ??? If I do not include the base- in the versions config it doesn't find it at all. > Second, what operating system are you using? Ubuntu 9.10. Notice the path names look better now. It isn't splitting up the version number. Thanks, Tim PS. I'm sure it's in the docs somewhere. But ..... I used pyxbgen to create my bindings before. The -base egg doesn't seem to provide pyxbgen, pyxbdump, etc. How would I generate bindings without the -full install? -- *************************************************************** Timothy Cook, MSc LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == (upon request) Academic.Edu Profile: http://uff.academia.edu/TimothyCook You may get my Public GPG key from popular keyservers or from this link http://timothywayne.cook.googlepages.com/home
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________ pyxb-users mailing list pyxb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyxb-users
