You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Jeff Hammerbacher (JIRA)" <ji...@apache.org> on 2010/03/19 10:23:27 UTC

[jira] Created: (AVRO-482) Improve and standardize process for publishing Python release artifacts to PyPI

Improve and standardize process for publishing Python release artifacts to PyPI
-------------------------------------------------------------------------------

                 Key: AVRO-482
                 URL: https://issues.apache.org/jira/browse/AVRO-482
             Project: Avro
          Issue Type: Improvement
          Components: python
            Reporter: Jeff Hammerbacher


We are now publishing Avro releases to PyPI. Let's make sure things work as planned.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (AVRO-482) Improve and standardize process for publishing Python release artifacts to PyPI

Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AVRO-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847292#action_12847292 ] 

Jeff Hammerbacher commented on AVRO-482:
----------------------------------------

* make the egg not depend on on Python 2.5
* replace "hammer" as Package Index Owner with some ASF-controlled account
* make "setup.py egg_info" command work so that "pip install avro" will work (currently breaks on how the version is read from a file in ../../share)

> Improve and standardize process for publishing Python release artifacts to PyPI
> -------------------------------------------------------------------------------
>
>                 Key: AVRO-482
>                 URL: https://issues.apache.org/jira/browse/AVRO-482
>             Project: Avro
>          Issue Type: Improvement
>          Components: python
>            Reporter: Jeff Hammerbacher
>
> We are now publishing Avro releases to PyPI. Let's make sure things work as planned.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (AVRO-482) Improve and standardize process for publishing Python release artifacts to PyPI

Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AVRO-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856667#action_12856667 ] 

Jeff Hammerbacher commented on AVRO-482:
----------------------------------------

It looks like the Java implementation uses

{code}
  <loadresource property="version">
    <file file="${basedir}/../../share/VERSION.txt"/>
  </loadresource>
{code}

To pull the VERSION.txt content into an Ant property. The <filter> can do token replacement in setup.py before calling {{python setup.py build sdist upload}}.

Will try out this trickery and post a patch if it works...

> Improve and standardize process for publishing Python release artifacts to PyPI
> -------------------------------------------------------------------------------
>
>                 Key: AVRO-482
>                 URL: https://issues.apache.org/jira/browse/AVRO-482
>             Project: Avro
>          Issue Type: Improvement
>          Components: python
>            Reporter: Jeff Hammerbacher
>
> We are now publishing Avro releases to PyPI. Let's make sure things work as planned.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (AVRO-482) Improve and standardize process for publishing Python release artifacts to PyPI

Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AVRO-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856169#action_12856169 ] 

Jeff Hammerbacher commented on AVRO-482:
----------------------------------------

One thought: perhaps we could use the <filterset> Ant task to perform the version number substitution...

> Improve and standardize process for publishing Python release artifacts to PyPI
> -------------------------------------------------------------------------------
>
>                 Key: AVRO-482
>                 URL: https://issues.apache.org/jira/browse/AVRO-482
>             Project: Avro
>          Issue Type: Improvement
>          Components: python
>            Reporter: Jeff Hammerbacher
>
> We are now publishing Avro releases to PyPI. Let's make sure things work as planned.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (AVRO-482) Improve and standardize process for publishing Python release artifacts to PyPI

Posted by "R. Tyler Ballance (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AVRO-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854722#action_12854722 ] 

R. Tyler Ballance commented on AVRO-482:
----------------------------------------

There are still issues with the latest 1.3.2-SNAPSHOT pushed to PyPI, the setup.py script references "../../share/VERSION.txt" which will not exist in the tarball, meaning it's impossible to cleanly `python setup.py install` the package

> Improve and standardize process for publishing Python release artifacts to PyPI
> -------------------------------------------------------------------------------
>
>                 Key: AVRO-482
>                 URL: https://issues.apache.org/jira/browse/AVRO-482
>             Project: Avro
>          Issue Type: Improvement
>          Components: python
>            Reporter: Jeff Hammerbacher
>
> We are now publishing Avro releases to PyPI. Let's make sure things work as planned.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (AVRO-482) Improve and standardize process for publishing Python release artifacts to PyPI

Posted by "R. Tyler Ballance (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AVRO-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849904#action_12849904 ] 

R. Tyler Ballance commented on AVRO-482:
----------------------------------------

For the purposes of integrating with setuptools or pip, it's important to make sure that a source tarball is pushed to PyPI for releases.

I've also had poor experience in the past with packages I maintain (such as Cheetah) where pushing an egg results in users getting broken installs with easy_install/pip

`python setup.py build sdist upload` should do the trick for you :)

> Improve and standardize process for publishing Python release artifacts to PyPI
> -------------------------------------------------------------------------------
>
>                 Key: AVRO-482
>                 URL: https://issues.apache.org/jira/browse/AVRO-482
>             Project: Avro
>          Issue Type: Improvement
>          Components: python
>            Reporter: Jeff Hammerbacher
>
> We are now publishing Avro releases to PyPI. Let's make sure things work as planned.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.